Linktotem now has an MCP server, which means you can manage your link in bio from Claude, Cursor or any other app that speaks MCP. Instead of opening the editor to add a link, you type "add my new episode at the top of the page" and the assistant does it. This article explains what that means, what you can ask for, how to connect it and where the limits are.

What's new, and why we built it

I spend my days inside ad managers, spreadsheets and chat windows. Opening one more dashboard to move a link from the third position to the first is small, but it adds up. More and more of that small work now happens by asking an assistant.

So we gave the assistant a way in. With the Linktotem MCP server connected, Claude or Cursor can read your page and change it: the header, the theme, the social icons and the blocks. It uses the same functions as the editor, so the same validation and the same safety checks apply. Nothing is done behind the editor's back.

What is MCP, in plain words

MCP stands for Model Context Protocol. It's an open standard for connecting AI applications to external systems, first introduced by Anthropic in November 2024. The official site compares it to a USB-C port: one standard plug, so any app that supports it can connect to any service that offers it.

In practice, a service publishes a list of "tools" (read this, change that), and the AI app decides which ones to call based on what you asked. You never see the plumbing. You write a sentence, the assistant picks the tool, and it tells you what it did.

Link in bio MCP: what you can ask

Our server has thirteen tools: five read, eight change something. These are examples of requests they cover, each one mapped to what actually happens:

1. "Add a link to my new episode at the top of the page: open.spotify.com/…" The assistant adds a link block at the top.
2. "Hide the ticket link, the event is over." The block disappears from the public page but isn't deleted, so you can bring it back later.
3. "Put the newsletter first and the social icons last." The assistant reads the page, then puts the blocks in the new order.
4. "Make the background dark and the buttons rounded." Only the parts of the theme you mention change; the rest stays as it was.
5. "Change my bio to: Freelance photographer in Lisbon, weddings and portraits." The header updates: name, tagline, bio, header layout or even the username (which changes your public address, so be sure).
6. "Add my TikTok and YouTube to the social icons." The row of icons on your home page is rewritten with the new ones included.
7. "Rename the 'Book now' button to 'Book a session'." One field of one block changes, nothing else.
8. "Who subscribed this week, and what did people answer in my form?" The assistant reads your subscribers and form responses, newest first.

You can also ask it to put a link inside a folder, add a heading or a text block, embed a video, or take a picture of your published page so it can comment on how it looks.

How to connect it

The setup takes a few minutes:

1. Be on Pro. The API and the MCP server are part of it.
2. Make an API key in Settings › API. Pick "read and write" if the assistant should change your page, or "read only" if you only want to ask questions about it. The key is shown once, so copy it while it's on screen.
3. Add the server to your app. Claude Desktop, Claude Code and Cursor each want it in a slightly different place.

The exact configuration for each app is on our help page, /mcp, ready to copy. I'm not repeating it here on purpose: it changes when the apps change, and the help page is the one we keep up to date.

A tip that saves trouble: start your first conversation with "read my page first and tell me what's on it". The assistant then knows the ids of your blocks and your current theme before it touches anything.

What it can't do (yet)

Being honest about the limits matters more to me than a long feature list.

• Some blocks stay in the dashboard. Through MCP an assistant can add links, headings, text, social icons, media and folders. Forms, email collection and the richer blocks (FAQ, testimonials, opening hours, map, bookings, price lists, products and so on) are made in the editor. The assistant can still read their responses, hide them, move them or delete them.
• No numbers on clicks and views. The MCP tools don't read your analytics. If you need views and clicks in a script, the REST API has them.
• No ChatGPT for now. ChatGPT's custom connectors, in developer mode, accept OAuth or no authentication. Our server is opened with an API key, so it doesn't fit. Until we add OAuth, use Claude or Cursor.
• No drafts. Every change is live on your public page immediately, exactly as if you had made it by hand.

Is it safe?

It's as safe as the key you give it, so here's how the keys work:

• Read or write. A read-only key can look but never change anything. A write key is needed for every tool that edits. If you only want an assistant to answer questions about your page, give it a read-only key.
• One key, whole account. A key reaches every page on your account. That's useful for agencies, but it's worth knowing.
• Revocable. You can revoke a key in Settings › API at any time, and it stops working.
• Rate limits. Each key can make 120 calls a minute, and at most 30 of those can change something. An assistant stuck in a loop hits that ceiling fast.
• Same rules as the editor. Changes go through the same validation and safety scan as edits made by hand. Deleting a block is permanent, so I'd ask the assistant to hide rather than delete when in doubt.

Who gets it

The MCP server is a Pro feature, together with the REST API and the AI page assistant. Pro, which also brings several pages and a custom domain, costs €12 a month with a 14-day free trial; see the pricing page.

Until then, you can build and publish a page for free, or use Starter from €5 a month after a 14-day free trial. When Pro opens, connecting an assistant is the three steps above.

If you're a developer, or you manage pages for clients and want to automate more than a chat window allows, look at the Linktotem API. It's the same service the MCP server uses, with analytics and an OpenAPI reference.