Skip to main content

Fractera

io.github.Fractera/deployVersion 1.0.0

Zero-Ops deploy of a private AI workspace to your own VPS — from your AI chat. Free and open-source.

Status

Responds328 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:37 UTC
Latency
328 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://www.fractera.ai/api/mcpResponds328 ms
No sign-in

Claude Code

claude mcp add --transport http deploy https://www.fractera.ai/api/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: deploy
Remote MCP server URL: https://www.fractera.ai/api/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"deploy","type":"http","url":"https://www.fractera.ai/api/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

6 tools

Tools of Fractera
Read-only
Idempotent
Open world
check_statusRead the current installation progress ONCE, on demand. Call this only when the user explicitly asks how the deploy is going (e.g. "what is the status", "did it finish") — never on a timer and never in a polling loop. The deploy takes 8-14 minutes and the authoritative status channels are the email pipeline + the dashboard; one read on request is enough. Returns the current step, the list of completed steps (~44 total in a full bootstrap), and whether installation is done or failed.NoYesNot declaredNot declared
get_project_infoProject reference / help desk about Fractera. Use this to answer ANY user question about what Fractera is, how it works, its architecture, components, modes, data ownership, pricing, use cases, partner program, etc. — especially while a deploy is running and the user wants to learn more. TOKEN-ECONOMY: call with NO arguments first to get the lightweight list of section ids+titles, then call again with a single `section` id to fetch just that section. NEVER try to fetch everything at once; pull only the section(s) relevant to the user question. Set `lang:"ru"` for Russian-speaking users.NoYesNot declaredNot declared
get_subdomainReturn the final entry address of the server once installation is complete. In phase-1 (IP-first) this is a plain-HTTP Admin URL of the form http://<IP>:3002 — the server has NO domain and NO HTTPS cert yet (attaching a custom domain with HTTPS is an optional later step the user does inside Admin -> Personal Domain). Call this once after check_status reports status="done".NoYesNot declaredNot declared
get_vps_recommendationReturn a single recommended VPS provider for users who do not yet have a server. Call this ONLY when the user explicitly says they have no server. The user buys the VPS at this provider and comes back with IP + password.NoYesNot declaredNot declared
register_and_deployRegister a new Fractera user and start the deployment of their server in one atomic call. Use this AFTER you have collected the user's email (entered twice for typo protection), server IP, and root password. Creates the User row (or reuses an existing one with the same email), creates a free Subscription, creates a ServerToken, wipes any previous installation on the target server, and launches bootstrap. The deploy is IP-first (phase-1): the server comes up on plain HTTP at http://<IP>:3002 in 8-14 minutes; it does NOT get a domain or HTTPS cert here (that is an optional later step inside the workspace). Returns session_id (for a single on-demand check_status read — do not poll) and server_token (so the user can recover via retry_deploy if anything breaks). Call this AT MOST ONCE per conversation.YesNoNot declaredNot declared
retry_deployRetry a failed deployment using a server_token (from the failure email, the deploy-progress UI, or the dashboard). Wipes the previous broken install and runs a fresh deploy on the SAME server. Returns a new session_id — poll with check_status. Use this when the user reports a failed deploy or pastes a server_token.YesNoNot declaredNot declared

Details

Registry status
Active
Published
Jun 3, 2026
Updated
Jun 3, 2026
Repository
Not given
Categories (suggested)
Developer toolsCloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing