Run CoreCMO inside your own assistant.

The two values you need

Field	Value
Server URL	https://corecmo.ai/.netlify/functions/mcp
Authentication	API key. Not OAuth.
Header	Authorization: Bearer cc_live_...
Your key	Create one at your account. Shown once, then unrecoverable.

If your client cannot set a header

Many MCP clients take a server URL and nothing else. For those, put the key in the URL and set authentication to none:

The server also accepts api_key or token as the parameter name. This works identically to the header.

The trade, stated plainly: URLs appear in logs and browser history in a way headers do not. Prefer the header where your client allows one. If you use the URL form and later want it out of circulation, revoke the key from your account and issue a new one; revocation takes effect on the next call.

What each error actually means

What you see	What it means	What to do
Does not implement OAuth	You chose OAuth in the connector. The server is fine.	Switch to API key, or to none with the key in the URL.
Missing API key	The client connected without passing a key.	Add the header, or re-add the connector with the key in the URL.
Invalid API key	The key does not match any issued key.	Check for a truncated paste. Keys start cc_live_.
This API key has been revoked	The key was cancelled from an account.	Issue a new one.
No active CoreCMO plan	The key is valid. The subscription is not active. This is not a connection problem.	Check billing on your account.
Rate limit reached	120 calls in the trailing hour, rolling.	Wait. It frees up continuously rather than resetting on the hour.

What to expect once it is connected

• The tools are the playbook, applied. Each one runs a method against your Brief and returns a finished artifact rather than advice. The method itself never crosses the wire.
• It reads your Brief, so fill the Brief first. A skill run against an empty Brief produces generic output, which is the most common disappointment on a first session. Start at the Operator Brief.
• Long-running skills return a job, then the artifact. A model call exceeds the synchronous limit, so a skill hands back a job_id and your assistant collects it a few seconds later. This is normal and it is not an error.
• 120 calls an hour, rolling, with sweep detection above 30 distinct tools in an hour. Ordinary work does not come near either.
• The catalogue moves. Modules and skills get added. Your assistant should read corecmo://catalogue at the start of a session rather than reasoning from a remembered list.