Skip to main content
The Autonomy MCP server exposes the Autonomy coding platform - projects, coding tasks, setup, and Full Mode - as Model Context Protocol tools that any MCP host can call: Claude Code, Claude Desktop, and others. Point your AI agent at it and it can pick a project, kick off a coding task, watch it run, pull the diff, and send the work to your developers - all without leaving the editor.

Quickstart

Connect the MCP to your client in two minutes.

Tool Reference

Every tool, grouped by domain, with params and returns.

Run a task

How a coding task flows from instruction to shipped PR.

Full Mode

Run your whole app against your staging backend.

​
What you can do

  • Manage projects - list connected repos, initialize a project’s workspace, add new ones.
  • Run coding tasks - start a task from a natural-language instruction, poll it, reply to it, read what the agent did, and pull the diff.
  • Set a project up - configure install / validate / dev commands and environment variables so the agent can build in it.
  • Enable Full Mode - serve the project’s whole front end in Autonomy while proxying API calls to your existing staging backend.
  • Ship - finalize a task and open or update the pull request for your developers.

​
How it works

The server is a thin adapter over Autonomy’s backend (FEI): every tool maps to one backend endpoint. No agent logic lives in the MCP server - orchestration, sandboxes, and PR creation all happen in the platform. The server authenticates the caller and forwards the request.
Because it is stateless, the conversation lives in your client and all durable state lives in the platform - so tasks you start over MCP show up in Studio and vice versa.
New to Autonomy? Start with the Quickstart, then read Run a coding task.