MCP server

Endpoint: https://linkmag.net/mcp. Transport: Streamable HTTP, stateless, POST only. Add it to your client as a remote MCP server.

Without a key, three tools work: audit_site, request_api_key and claim_api_key. Everything else needs an API key in the connection's Authorization: Bearer <key> header. Tools never take a key as an argument. claim_api_key does return the new key once in its result, so it appears in the chat transcript; to keep it out, claim the key with the shell client or the REST API instead.

Getting a key from inside a chat

Call request_api_key. Show the user the code and link it returns.
After they approve, call claim_api_key with the request_id and device_code. The key is in the result, and therefore in the transcript.
The user adds the key to this connector's headers. Clients that cannot set headers can use the shell client or the REST API instead.

Tools

Tool	Key	What it does
audit_site	no	Audit a page's Open Graph tags
request_api_key	no	Start a key request
claim_api_key	no	Claim the key after approval
list_sites	yes	Sites on the account
create_site	yes	Create a site
get_site	yes	Site, domains with verification instructions, usage
delete_site	yes	Delete a site
register_domain	yes	Add a hostname, returns the DNS record and meta tag
verify_domain	yes	Check DNS, then the meta tag
remove_domain	yes	Remove a hostname
get_install_snippet	yes	Install code for a framework
render_preview	yes	Card URL for a path
set_template	yes	Layout, colors, logo, caption, badge
get_usage	yes	Renders this month
purge_cache	yes	Drop cached cards (Pro, Business)

Each result is markdown text plus structuredContent with the same data. Failures come back as tool errors whose text names the fix.

Agents can request any page on this site as markdown by sending Accept: text/markdown.