API and MCP reference

connect0 is drivable programmatically two ways: a public REST API and the MCP (Model Context Protocol) server. This page is a pointer — the exhaustive, always-current reference is served from the API host itself; here you get the hostnames and a quick tour of the main MCP tools.

Service hostnames

connect0 splits its programmatic surfaces across dedicated hosts, so a credential minted for one never works against another:

Host	Purpose
api.connect0.ai	Public REST API — the peer surface to MCP
mcp.connect0.ai	MCP server — tools for agents and MCP clients
webhooks.connect0.ai	Inbound webhook receiver (e.g. Stripe, source events)

The full REST reference (every route, request/response shape) is published from api.connect0.ai — treat it as the source of truth for REST. This docs site covers concepts and tasks, not the generated endpoint list.

Connecting an MCP client

Point any MCP client (Claude Code, Cursor, or a generic MCP client) at https://mcp.connect0.ai/mcp (Streamable HTTP). The server advertises its OAuth metadata for authorization; your client walks the standard MCP auth flow to obtain a token. Agents you install authenticate with their own client credentials — see Access model.

Main MCP tools

A quick reference to the primary tools the MCP server exposes. This is an orientation list, not the authoritative schema — connect an MCP client to enumerate the live tool set with full input schemas.

Tool	What it does
account.create	Create a new account
project.create	Create a project in an account
invite_member	Invite a human member to an account
connector.add	Add a connector to a project
connector.list	List a project's connectors
connector.refresh	Re-materialise a connector's data
connector.remove	Remove a connector
upload.create_link	Mint a pre-signed upload link
upload.write	Write a small file inline
download.create_link	Mint a pre-signed download link
info	Read sandbox / project info
sh	Run a shell command in the project sandbox
web_fetch	Fetch a URL (metered)
datetime	Current date/time helper
billing.start_checkout	Start a credit checkout
connect0_search_docs	Search this documentation

Zero, the connect0 assistant, exposes additional connect0_* tools (setup, usage, credits, run explanations) used to drive the product conversationally.

Versioning, deprecation, and rate limits

The REST surface is URL-versioned under /v1. You can rely on this contract:

• Breaking changes never land inside /v1 — they ship under a new version prefix.
• Operations scheduled for removal are marked deprecated in the OpenAPI document at api.connect0.ai/openapi.json before they are removed, and removals are announced in the release notes.
• Every /v1 response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers; a 429 also carries Retry-After. Clients — human or agent — should self-throttle from these headers.
• Every error (4xx/5xx) is a JSON envelope { "error": { "code", "message", "request_id" } }, never HTML. The ErrorResponse schema in the OpenAPI document is the typed contract.

Where to go next

• Create an agent — stand up an agent that uses these tools.
• Connect a source — wire up the connectors the connector.* tools operate on.