blog

Introducing Coaade MCP: bring your own AI to Coaade

ProductNovember 11, 20265 min

Plenty of developers already pay for an AI tool they like: ChatGPT, Claude, Claude Code, Kiro, Cursor, VS Code with Copilot. What those tools don't come with is somewhere for the code to live and run: a workspace, a terminal, a database, hosting, a deploy button. Coaade has all of that. Today we're connecting the two with Coaade MCP.

What it is

Coaade MCP is a remote server for the Model Context Protocol, the standard way AI tools call outside tools. Point your AI tool at it with a Coaade API key, and its AI can work on your Coaade projects the way Coaade's own AI does in the IDE. It gets 57 tools in 12 groups:

  • Files and terminal: read files in line ranges, search with regex, write and edit files, and run builds, tests and installs in the project's cloud Linux workspace.
  • Ship it: deploy to *.coaade.app, read build logs and set environment variables; create PostgreSQL, MongoDB and Redis databases; commit and push to GitHub.
  • Check it: run App Test, which uses the deployed site in a real browser and reports what broke, or a security scan, a non-destructive check of your own site's headers, cookies, CORS and exposed files.
  • The rest of Coaade: project memory, scheduled tasks, Copilot CTO's proposals and reports, and plan usage.

Your subscription thinks, Coaade runs it

The AI work stays with the tool you already pay for: it reads, plans and writes. Coaade provides the parts that need a server: the workspace, the terminal, the databases, the hosting and the GitHub connection, within your Coaade plan. Two tools are the exception, because they run Coaade's own AI: ask_coaade hands a task to Coaade Code, and run_app_test runs the AI tester. Those count against your Coaade AI allowance as usual.

Set up in a minute

In ChatGPT or Claude, add a custom connector with the URL https://api.coaade.com/mcp. Your tool sends you to coaade.com: sign in, choose full access or read only, and press Allow, like connecting any plugin. In Claude Code it's one command, and tools that take a header can use an API key from the IDE's MCP page instead:

claude mcp add --transport http coaade https://api.coaade.com/mcp
# then /mcp in Claude Code → Coaade → sign in with Coaade

Kiro, Cursor and VS Code take a few lines of JSON. The setup docs have each one.

What a session looks like

You:    List my Coaade projects, add a contact form to my-site,
        deploy it and check the form works.

Claude: list_projects → my-site (static, live at my-site.coaade.app)
        read_file index.html, search_files "form"
        write_file contact.html, edit_file index.html (nav link)
        run_command npx html-validate *.html → exit code 0
        deploy → https://my-site.coaade.app
        run_app_test "Open Contact, fill in the form, submit, check
                      the thank-you message" → PASS

Every step lands in your Coaade project, so you can open it in the IDE afterwards and see exactly what changed.

Safe by default

  • Read-only keys. Give a tool look-only access: it sees files, logs, state and test results, and can't change anything.
  • It acts as you. A key has your plan's limits and your role on shared projects, so a project you can only view stays read-only.
  • It asks before it destroys. Deleting files or databases and taking a site offline are marked, so your tool asks you first.
  • Logged and revocable. Every call is logged, and disconnecting an app or revoking a key stops it at once.

One server for all of Coaade

We named it Coaade MCP, not after a single product, on purpose. It's one server for your whole Coaade account. As Coaade adds products, their tools join the same server, so the setup you add today keeps working.

Availability

Coaade MCP is on every plan, including Free, at https://api.coaade.com/mcp. App Test and Copilot CTO need Pro or above, as they do in the IDE.