INDIVIDUAL MCP TOOL

register_and_deploy

fractera.ainone authenticationAvailability not checked

Input schema

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.fractera-installer]
url = "https://www.fractera.ai/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "fractera-installer": {
      "type": "http",
      "url": "https://www.fractera.ai/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: fractera-installer
Remote MCP URL: https://www.fractera.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "fractera-installer": {
      "url": "https://www.fractera.ai/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "fractera-installer": {
      "type": "http",
      "url": "https://www.fractera.ai/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "fractera-installer",
  "transport": "streamable-http",
  "url": "https://www.fractera.ai/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

check_status — Read the current installation progress ONCE, on demand.
get_subdomain — Return the final entry address of the server once installation is complete.
retry_deploy — Retry a failed deployment using a server_token (from the failure email, the deploy-progress UI, or the dashboard).
get_vps_recommendation — Return a single recommended VPS provider for users who do not yet have a server.
get_project_info — Project reference / help desk about Fractera.
get_ai_workspace_architect_info — Architecture reference for Fractera AI Workspace: what it is made of and how it works (the admin drives it through Hermes — chat Web UI or Telegram — or directly through the five coding agents; a modal subscription sign-in layer + MCP keep work resilient when a subscription is limited; LightRAG is the central memory that slashes token use; Hermes is a light orchestrator while the coding agents do the heavy lifting; the result ships over HTTPS on a custom domain or plain HTTP on an IP).
get_ai_development_loop_info — Explains the Fractera development loop: how one admin request becomes tested, deployed, recorded code with no human writing it — Hermes orchestrates and loads its identity + project context, picks a ready coding agent (Claude Code, Codex, Gemini, Qwen, Kimi), the agent is enriched (SOUL.