MCP and API
Connect to Iter0 with MCP
Find the MCP endpoint, create an API key, inspect the available tools, and understand what a successful connection proves.
By Iter0 · Updated 2026-09-21
On this page
Before you connect
Iter0 exposes a remote MCP server and a downloadable local server. To use account-owned creation or editing tools, sign in and create an API key from the API keys page. The full key is shown once. You can revoke it later, but current keys do not have separate permissions for individual tools.
Choose a connection
For a client that supports remote Streamable HTTP MCP, use the Iter0 endpoint below. The server accepts JSON-RPC over POST. A normal browser GET request is not a connection test and returns Method Not Allowed. If your client expects a local command, use the Node, shell, or PowerShell installer on the MCP setup page and copy the configuration it prints.
https://iter0.com/api/mcpInspect the advertised tools
After initialization, ask your client to list tools. The remote server currently advertises the four tools below. Health and developer guidance help inspect the connection. Website creation and editing require an authenticated Iter0 API key and may use credits.
- sitesorted_health
- sitesorted_create_site
- sitesorted_edit_site
- sitesorted_get_developer_docs
Limits of a connection check
A successful initialize request and tool list prove that the MCP transport and discovery path responded. They do not prove that a paid website creation or edit completed. Check the result returned by the exact tool call, including any authentication, credit, provider, or generation error, before treating the requested change as complete.
The local downloadable server and remote server do not advertise exactly the same helper tools. Client configuration examples are provided for several clients, but availability still depends on the MCP features and configuration format supported by the client version you are using.