Why has my systeme.io AI connection stopped working?

The cause every key eventually has in common

systeme.io states plainly that, for security reasons, MCP keys are valid for a maximum of 90 days. There is no way to issue one that lasts longer. A connection that worked for weeks and then stopped, with nothing else changed, has most likely just reached that date.

No article says whether systeme.io sends any warning before a key expires, the way it does before a contact-limit restriction. As far as the documentation goes, the 90-day clock runs out with no announcement.

An account can hold two MCP keys at a time. Making a fresh key ahead of an expiry, rather than waiting for the old one to stop working, is the practical way around this, though systeme.io's two-key cap means an old one may need deleting first if the account is already at that limit.

ChatGPT's own troubleshooting list

Of the two AI tools systeme.io documents, only the ChatGPT guide carries a troubleshooting section. It names exactly two things to check if the server fails to connect:

• The MCP key is valid and not expired, and was entered correctly.
• Developer Mode is switched on in ChatGPT's own settings, under Apps and Connectors, then Advanced settings.

systeme.io has no official ChatGPT app, so the connection runs through Developer Mode as a custom app. That setting lives entirely on ChatGPT's side, and systeme.io's article does not say what would cause it to turn itself off, only that it is worth checking.

Claude has no equivalent published checklist

systeme.io's guide for connecting Claude describes the setup and the permission levels available in Claude's own connector panel, and nothing else. No troubleshooting section exists for it. The two general causes above, an expired key and a setting on the AI tool's side, are what its documentation leaves you to check, since the permission switches for a connection are described as living in the AI tool rather than in systeme.io.

Something that looks the same but is not the connection breaking

A busy stretch of commands can trigger a rate limit rather than a real disconnection. The MCP server shares one request quota across all of an account's keys, and going over it returns a 429 Too Many Requests response rather than any kind of connection failure. That resolves on its own once the quota refills, which an expired key never does.