MCP Server

Your site's own MCP server at /mcp: any agent connects without a key and sees your buyer-facing tools only; your operator tools answer only to a signed request. What each caller sees, the limits, and how to verify.

MCP Server

Every site on Inception Agents answers the Model Context Protocol at https://your-domain.com/mcp, and /.well-known/mcp.json points agents there. It is how an agent that never opens a browser (a personal agent working for someone, a chat connector) reads your answers and completes a request on your site, often while nobody is watching. The tools are your Agent Actions, the same ones your pages register, from the same configuration.

/mcp is served on your own domain by the WordPress plugin, the Cloudflare Worker, or our edge.

Who sees what

Privilege follows proof, never a header’s presence.

Caller	How it is recognised	What it sees
Any agent (personal agents, chat connectors, browsers on your page, anything else)	Nothing needed: no key, no sign-up	Your buyer-facing tools only: the read tools (`get_briefing`, `ask_site`, one `get_{slug}` per published point), your action tools (`request_`, `book_`, `confirm_request`, `confirm_booking`), and nothing outside what fits your kind of business: a law firm’s site never offers a cart
Your own signed request	A request signed with your own key through the SDK route-through, and verified	The full registry, operator tools included

Your operator tools (analytics, audiences, campaigns and spend) answer only to that verified signature. An Authorization: Bearer … header is not a credential on this endpoint at all, so a made-up token gains nothing. Signature headers that fail verification are treated like any other public caller.

Behind the plugin or the Worker, each request reaches us signed with your site’s relay key, together with the visitor’s address, Origin and User-Agent, so each visitor is counted and rate-limited as themselves. A relay vouches for the visitor; a relayed request is never treated as signed, so a relay never gains operator powers.

Your own team uses the operator tools from its own Claude, through the Inception Agents connector at mcp.inceptionagents.com, which signs you in to your workspace. Ask it what came in today, what agents asked your site this week, or to take your site live.

Completing a request

An agent completes a request the way the approval table describes:

With the person’s details and go-ahead in hand, it sends their name, a phone or email, and consent_contact = true with the request tool, and gets the receipt back: Confirmed. Reference IA-7KQ2ZM. The business has your request and will respond within one business day.
Without them, the request tool returns a reference, and the agent completes it with confirm_request once the person agrees. A time against a connected calendar is always this second step (confirm_booking), because the person or their agent picks one of the offered times.

Every lead records how it was approved (agent_authorized for an agent’s relay). An agent can complete a request, and you can answer it, but it cannot opt anyone into your marketing: only the person’s own tick on the card on your page does that.

Limits

120 calls a minute per address, and 10 a minute for tools that create a request or are metered. An agent that goes over is told to wait, and nothing is sent.
A client that has not signed its request may send one tool call per JSON-RPC batch; the others come back with an error asking for separate requests.
One contact can complete five requests with you in 24 hours, counted by phone number as well as by the full contact.

What is recorded

With recording on (the default for a new workspace), each agent visit through your tools, on /mcp, on your pages or at /agent/*, is recorded in your workspace as one agent conversation: what it asked, exactly what it was told, whether that was a real answer, and how far it got (found, understood, chosen, acted, delivered). Contact details in an agent’s question are masked when it is recorded, and answers are kept 365 days by default. Your own signed calls are not recorded as conversations.

Verify

# Agents are pointed at /mcp
curl -s https://your-domain.com/.well-known/mcp.json

# The tools any agent is offered, without a key
curl -s -X POST https://your-domain.com/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Standard MCP clients connect too. Going live runs this check with a standard MCP client from outside, and repeats it every hour once your site is live: the tools your site serves must be the ones you approved. The lookups for the answers you publish are approved as a group, so a new answer never needs a new approval.