Connect an AI assistant

Last updated: 20 September 2026

What this is

Edition House publishes a remote Model Context Protocol server. An AI assistant that speaks MCP can connect to it, and the person who owns the Edition House account decides whether to allow that and what it may do.

Once connected, the assistant can answer questions about the business's search performance and compliance findings, and can queue an article draft for review. It acts as the person who authorised it, on that person's own business, and on nothing else.

Endpoint

https://www.edition.house/mcp

Transport is Streamable HTTP. The server is stateless: every request carries its own bearer token and no session id is issued. POST carries JSON-RPC. GET answers 405, because the server never initiates a message.

A request without a valid token answers 401 with a WWW-Authenticate header naming the protected-resource document, which is how a client discovers where to authorise.

Authorisation

OAuth 2.1 with PKCE (S256, required — there is no plain fallback and no implicit flow). Clients may register dynamically; no manual onboarding step is needed.

Discovery

GET /.well-known/oauth-protected-resource/mcp   (RFC 9728)
GET /.well-known/oauth-authorization-server     (RFC 8414)

Endpoints

POST /api/oauth/register    dynamic client registration (RFC 7591)
GET  /api/oauth/authorize   consent, then an authorization code
POST /api/oauth/token       code + PKCE verifier, or refresh
POST /api/oauth/revoke      revocation (RFC 7009)

The token endpoint takes application/x-www-form-urlencoded, as RFC 6749 requires. An access token lasts one hour; the refresh token rotates on every use and lasts sixty days.

Permissions

Three, shown separately on the consent screen so that reading and writing are never one decision:

content:read — tracked pages, their ranks, and the recommended next actions.
compliance:read — open compliance findings, and checking supplied text against the regulator's rules.
content:write — queueing an article draft for review. Nothing is published.

A connection granted only the read permissions is not offered the write tool at all: tools/list returns what the grant can actually run, so an assistant cannot promise something that would then be refused.

Tools

Tool	Permission	What it does
`list_pages`	content:read	Lists the pages Edition House tracks, each with its search rank for its target keyword and the market that rank was measured in.
`get_recommendations`	content:read	Returns the ranked queue of what to do next to existing pages — the same order the Edition House app shows.
`list_compliance_issues`	compliance:read	Lists open compliance findings across web pages, LinkedIn posts and ads, with the phrase and the rule each one engages.
`check_text`	compliance:read	Checks supplied marketing copy against the business's regulator rules before it is published. The text is not stored.
`create_draft`	content:write	Adds an article to the Write queue as a draft for a person to review. It publishes nothing.

Every tool declares its read-only, destructive, idempotent and open-world hints. Four of the five are read-only; the fifth adds a draft and changes nothing that already exists.

What a connected assistant never receives

Google Analytics data does not cross this boundary. No conversion count, no conversion rate, no goal verdict, and no result that a goal decided is available to any tool, at any permission level. A tool result becomes prompt text inside the connected assistant, and Edition House commits in its Privacy Policy (sections 4 and 6.3) to one single place where analytics data reaches an AI provider — the weekly report's summary paragraph. This connector is not that place, and a test in the codebase holds the tool schemas to it.

Nor does a connected assistant receive another customer's data. Every tool query is filtered to the one business named in the grant, and that business came from the membership of the person who approved the connection.

Limits and requirements

An Edition House account with a business already set up. A new account with no site connected has nothing to report.
check_text needs a regulator configured for the business. Without one it refuses and says so, rather than returning a clean result it cannot stand behind.
create_draft is bounded by the account's plan. When the allowance is spent, it refuses and queues nothing.
Compliance findings are advisory. Edition House is not a law firm and a finding is a prompt to review, never a legal opinion.
Rank is reported for one named market at a time. Two markets are never merged into a single number.

Disconnecting

The person who authorised a connection can revoke it in Edition House settings, and the assistant stops working immediately. A client may also revoke its own tokens at /api/oauth/revoke.

Support

Email hello@edition.house. See also our Terms of Service and Privacy Policy.