Linktotem

MCP

Ask for it, and the page changes

Linktotem speaks MCP, so Claude, Cursor or any client that does can read your page and change it. “Add my new episode at the top” is a sentence, not a session in the editor.

There are no drafts

Every change an assistant makes is live on the public page at once — the same as editing it by hand. Ask it to read the page before it changes anything, and to tell you what it did.

How it works on your page

Your assistant works the way a designer would: it looks before it touches, and checks after.

  1. 01Reads the page and checks it: broken links, example content, colours that are hard to read.
  2. 02Changes it, starting from one of our templates on an empty page, with our fonts and palettes.
  3. 03Looks at the result on a phone and on a desktop, the whole page, even before you publish.
  4. 04Checks again and fixes what is left, then tells you what it changed.

Setting it up

Claude.ai and ChatGPT: no key needed

Both connect with your Linktotem sign-in (OAuth). Add this address as a connector:

MCP server address
https://linktotem.com/api/mcp
  • Claude.ai and the Claude app: open Linktotem in the Claude directory, then Connect. You can also add the address as a custom connector.
  • ChatGPT: Settings › Apps & Connectors › Advanced settings, turn on developer mode, then Create, paste the address and choose OAuth.

Linktotem opens: sign in, choose whether the assistant may change your page or only look at it, and allow. You can disconnect it any time in Settings › API.

Claude Desktop, Claude Code and Cursor: with a key

  1. Be on Pro: the API and the MCP server are part of it.
  2. Make a key in Settings › API. Choose “read and write” for an assistant that should change the page; “read only” is enough to ask questions about it.
  3. Put the key in your client's configuration, below. It is shown once, so paste it while it is on screen.
Claude Desktop — claude_desktop_config.json
{
  "mcpServers": {
    "linktotem": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://linktotem.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer app_live_…" }
    }
  }
}

The key lives in `env`, not in `args`: on Windows the space in “Bearer x” gets mangled on the way to npx, which is why the header is split in two.

Claude Code
claude mcp add --transport http linktotem https://linktotem.com/api/mcp \
  --header "Authorization: Bearer app_live_…"
Cursor — ~/.cursor/mcp.json
{
  "mcpServers": {
    "linktotem": {
      "url": "https://linktotem.com/api/mcp",
      "headers": { "Authorization": "Bearer ${env:LINKTOTEM_KEY}" }
    }
  }
}

Cursor resolves environment variables inside headers, so the key stays out of a file you might commit.

Things to say

Two shortcuts

Claude Desktop and Claude Code show them as commands once the server is connected.

The tools

On the same limits as the API: 120 calls a minute per key, of which 30 may change something. The ones marked as changing the page tell your assistant to ask you first when they can lose something.

Your page, one sentence away

Make an account, get a key, and point your assistant at it.

Claim your link today

One link for everything you create, sell and share. Free to publish, online in minutes.