Systeme.io publishes one MCP integration guide, and it is for ChatGPT. There is no Claude guide in its developer documentation. The connection still works, because the server is an ordinary remote MCP server and Claude accepts those as custom connectors — but you assemble the steps from two vendors instead of one, and a couple of details only become obvious once you know where each side draws its line.
Two of those details are worth knowing before you start. The Systeme.io documentation describes key-based authentication with the key in the connector URL, while the live server now answers with an OAuth challenge carrying an mcp:full scope — so follow whatever your client negotiates rather than the published flow. And Claude reaches a remote MCP server from Anthropic’s own cloud rather than from your laptop, on every client including the desktop app. Neither blocks you. Both change how you think about the credential.
Get the key
Open your Systeme.io dashboard, go to profile settings, and find the "MCP & API keys" section. Generate a key there and keep it somewhere you would keep a password, because for the next few minutes it is going to sit in a URL.
The server supports two ways of presenting that key: an X-MCP-Key HTTP header, or an mcpKey query parameter on the URL. Systeme.io documents both, and explains that the query-parameter route exists because some MCP clients cannot set custom headers. Claude’s custom-connector form takes a server URL, so the query parameter is the route that fits.
Add it to Claude
On a Free, Pro, or Max plan, open Customize, then Connectors, click the plus button, and choose "Add custom connector". Paste the server URL with your key appended — the address is https://mcp.systeme.io/mcp and the key rides as the mcpKey parameter. Leave the optional OAuth client fields empty, because this server does not use OAuth. Click Add.
Team and Enterprise plans work differently. Only an Owner or Primary Owner can add a custom connector, from Organization settings rather than personal settings, and members then connect to it individually once it exists. Free plans are capped at a single custom connector, so if you already have one you will be choosing between them.
Connectors are enabled per conversation rather than globally. Use the plus button in a chat, open Connectors, and toggle Systeme.io on for that conversation. There is also no edit: changing a connector means removing it and adding it again, which is the step you will take whenever you rotate the key.
Where the connection actually comes from
Anthropic documents something easy to miss. When Claude uses a custom connector, the request originates from Anthropic’s cloud infrastructure, not from the machine you are sitting at — and that holds for claude.ai, the desktop app, and mobile alike. Local MCP servers configured through a desktop config file are a separate mechanism that does use your own network.
For Systeme.io this changes nothing operationally, because mcp.systeme.io is a public address that Anthropic’s infrastructure can reach. It matters for what it implies about the key. The credential is held in a connector configuration and used from a remote system on your behalf, which is a good reason to treat rotation as routine rather than as something you do after a scare.
The connection path, end to end
Generate the key
- Systeme.io dashboard, profile settings
- "MCP & API keys" section
- Treat it as a password — it will sit in a URL
Add the custom connector
- Claude: Customize, then Connectors
- Plus button, "Add custom connector"
- Server URL with the key as mcpKey
- Leave the OAuth fields empty
Enable it per conversation
- Plus button inside a chat, then Connectors
- Toggle Systeme.io on for that conversation
Put it to work
- Contacts, tags, contact fields, newsletters
- Products, offers and funnels — undocumented but working
- Test on throwaway records first
- Confirm deletions yourself
What you can actually ask for once it is connected
The documentation lists contact and newsletter management and calls that the complete set. The working surface is wider — products, offers and funnels can be created by conversation too, which no published page yet describes.
- Contacts: list, retrieve, create, update, delete.
- Tags: list, retrieve, create, update, delete, and assign or remove them from contacts.
- Contact fields: list the available fields and their slugs.
- Newsletters: create, update, find, and review existing ones.
- Digital products, offers and funnels: demonstrated working, though undocumented.
The same capabilities also exist in the Systeme.io REST API, a separate surface of roughly 125 endpoints reached by writing code. The useful discovery is that you often do not need it: an assistant connected over MCP can reorganise who is on your list, what goes out to them, and — undocumented but working — the product, offer and funnel they arrive through. Treat the undocumented half carefully, since nothing published tells you its edges.
Rate limits follow the public API policy, and the quota is shared across every key on the account rather than allocated per key. Requests report their remaining allowance in response headers, and exceeding the ceiling returns 429. Conversational bulk edits are many individual calls, so a run across several thousand contacts is worth doing in observable batches.
Two habits worth keeping
Connect only to servers you trust, and stay aware that a compromised or careless MCP server can attempt to steer an assistant through hidden instructions in the data it returns. Anthropic names prompt injection explicitly in its custom-connector guidance and ships protections against it, and the sensible posture is to read what a tool actually did rather than assume. Systeme.io is a first-party server for an account you already control, which is about as good as the trust picture gets — the habit still belongs in place before you add the second connector.
The second habit is narrower: confirm destructive actions yourself. Contact deletion is in scope for this server, and a request phrased loosely enough to be misread is a request that can remove people from a list you spent money building.
Technical disclosure
The documented Systeme.io facts were read from its developer documentation on 27 September 2026, where the MCP server page carried a last-updated date of 8 June 2026 and an initial-release status notice; no Claude-specific integration guide existed there on that date, so the Claude-side steps come from Anthropic’s custom-connector guidance, last modified 11 August 2026. The product, offer and funnel operations are reported from running them against a live account, not from any published page, and the OAuth challenge was observed directly from the live endpoint. Where documentation and server disagree, the server is the authority. Interface labels and capability lists move without announcement, so test before relying on any of it.
Audit your page free, then let the assistant handle the list behind it.