What is an MCP, and why your link in bio should have one

An MCP is the open standard that lets an AI assistant like Claude actually do things inside another app, not just talk about them. A link in bio MCP means you can tell your assistant "add my new song to the top of my page" and it happens, because the assistant can reach your page through the isall.me MCP server.

That is the whole idea. This post explains what an MCP is in plain terms, and how the isall.me one works. It is written by the person who builds isall.me, so I will keep it honest about what it does and does not do.

What MCP actually stands for

MCP is short for Model Context Protocol. It is an open standard, not an isall.me thing. Anthropic published it, and lots of tools now support it.

Here is the simplest way to think about it. Your AI assistant is smart, but on its own it can only read and write text in the chat window. It cannot open your accounts or change anything in the real world.

An MCP server is a little bridge. It sits between the assistant and an app, and it hands the assistant a set of buttons it is allowed to press. Each button is called a tool.

So when someone says "the isall.me MCP," they mean a small program that exposes tools like "read my page" and "update my page" to your assistant. You talk to the assistant. The assistant presses the buttons. Your page changes.

Why a creator, not just a developer, would care

You do not need to write code to use an MCP. That is the part people miss.

Once the isall.me MCP is connected to your assistant, you just ask for things in normal words:

• "Pin my new YouTube video to the top."
• "Change my bio to mention the tour dates."
• "Add a link to my Bandcamp and label it Listen."

The assistant reads your current page, figures out the change, and writes it back through the MCP. You review the result. No dashboard clicking, no copy-paste.

It feels less like using software and more like asking an assistant who happens to have access to your page.

What the isall.me MCP can do

The isall.me MCP server exposes tools to read and update your page. So your assistant can look at what is there now and make changes for you.

That covers the everyday stuff: links, order, labels, your bio, and swapping things in and out. If you can do it in the dashboard, the goal is that you can ask for it in chat.

It is a live product on npm. You do not build it yourself, you just point your assistant at it.

How to connect it

You need two things: a token, and the MCP server added to your assistant.

1. Mint a token. In your isall.me dashboard, open the Developer tab and create a token. It starts with isam_. This is a Pro feature, and there is a read-only option if you only want the assistant to look, not touch. Treat the token like a password.

2. Add the MCP server. The server lives on npm as isallme-mcp. Most assistants let you add an MCP server by giving them a command to run. The command is:

npx -y isallme-mcp

You give it your isam_ token so it knows which page to act on. Your assistant's own docs will show where MCP servers get added, since every app puts that setting in a slightly different place.

Once it is connected, try something small first, like changing a link label, so you can see the loop work before you trust it with more.

MCP, CLI, and API: how they relate

isall.me gives you three ways in, and they overlap on purpose.

• The MCP is for talking to your page through an AI assistant. Best when you want to describe a change in words.
• The CLI (isallme on npm, run with npx isallme) is for the terminal and for scripts. Best when you want to type exact commands or wire something into a scheduled job.
• The API (the REST API at https://isall.me/api/v1) is the raw layer both of the others sit on. Best when you are building your own thing.

They all use the same isam_ token. Pick whichever matches how you like to work. Full docs for all three live at the hub: https://isall.me/developers.

If you are curious how this plays with a specific assistant, the walkthrough at /blog/link-in-bio-claude-mcp goes step by step. And if you want the assistant to run on its own schedule instead of only when you ask, /blog/ai-agent-link-in-bio covers that.

The honest limits

An MCP is a bridge, not a magic wand. A few things worth saying plainly.

The assistant only does what you ask, and it can misread a request, so review changes before you rely on them. The read-only token exists for exactly this reason: you can let the assistant look without letting it edit.

There is also no built-in one-click auto-poster here. The MCP gives the assistant the tools to make changes; if you want things to happen automatically on a timer, that is you wiring an agent or a script to those tools, which is a different setup.

And it is a Pro feature. Developer access, including tokens, comes with Pro, which is 24 dollars a year with a 0 percent fee on tips and sales.

FAQ

Do I need to be a developer to use the isall.me MCP?

No. That is the point of MCP. You connect the server once, then ask your assistant for changes in plain language. The assistant handles the technical part. The only slightly technical step is adding the MCP server to your assistant, and your assistant's docs walk you through where that setting lives.

Is MCP an isall.me invention?

No. Model Context Protocol is an open standard from Anthropic that any app can support. isall.me built an MCP server for its pages, but the protocol itself is shared across the industry, which is why the same assistant can use many different MCP servers.

Is the MCP safe to connect?

It is as safe as the token you give it. Tokens are scoped to your account, you can create a read-only one so the assistant can look but not edit, and you can revoke a token any time from the Developer tab. Treat the isam_ token like a password and do not paste it in public.

What is the difference between the MCP and the CLI?

The MCP is for asking your AI assistant to change your page in words. The CLI is for typing exact commands in a terminal or running them in a script. Both do the same underlying work and use the same token. See /blog/link-in-bio-cli if the terminal is more your speed.

Try it

Claim your link, then open the Developer tab and mint a token to hand your assistant. Start free, and upgrade to Pro when you want developer access.

Create yours at https://isall.me/signup and read the full developer docs at https://isall.me/developers.

Everything you are. One little link.