Connect ContentIn to your AI tools

2. Add the server to your client

One remote server, the same for every client. Replace YOUR_KEY with the key you just created.

Server URL

https://cms.contentin.io/mcp-server

Transport

Streamable HTTP

Auth header

X-MCP-Key: YOUR_KEY

Key format

cimcp_…

claude mcp add contentin --transport http https://cms.contentin.io/mcp-server --header "X-MCP-Key: YOUR_KEY"

{
  "mcpServers": {
    "contentin": {
      "type": "http",
      "url": "https://cms.contentin.io/mcp-server",
      "headers": {
        "X-MCP-Key": "YOUR_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "contentin": {
      "url": "https://cms.contentin.io/mcp-server",
      "headers": {
        "X-MCP-Key": "YOUR_KEY"
      }
    }
  }
}

3. What you can do

Eight tools. Your assistant picks the right one from what you ask — you never call them by name.

Prompts to start with

Paste any of these into your client once the server is connected.

• “What have I got scheduled for next week, and what did my last three published posts do?”
• “I ran a workshop today and two people asked the same question about pricing. Write me a post about it in my voice.”
• “Save this for later: our churn dropped from 6% to 3.4% after we moved onboarding to a live call.”
• “Give me five post ideas based on the topics that performed best for me this month.”
• “Take my best-performing post from the last 90 days and repurpose it from a different angle, then schedule it for Tuesday at 9am CET.”

4. What the server will and won't do

5. Troubleshooting

"Invalid key" or the tools refuse to run

Re-copy the key from ContentIn → Settings → "Connect AI clients". The most common cause is a truncated paste or a stray space at the start or end of the header value. Keys start with cimcp_. If you no longer have the key, create a new one — the original is only ever shown once — and revoke the old one while you're there.

"Requires Pro" when the tools are called

The MCP server is part of the ContentIn Pro plan, and the server checks your plan live on every call. If you've just upgraded, the tools start working on the next call — no need to create a new key or restart your client. If you're not on Pro yet, start a trial and the same key works the moment the plan is active.

I hit the rate limit

Each key has a daily call ceiling that resets at 00:00 UTC. Wait for the reset, or spread the work out. If an assistant burned through it in a loop, it's worth checking what it was retrying — the limit exists precisely to make that visible.

The server connects but there are no posts or analytics

Check that the profile the key belongs to has a connected LinkedIn account, and that you have posts in ContentIn. Analytics are collected on a schedule and only for posts published through a connected LinkedIn account, so a post published a few minutes ago will honestly report that it hasn't been measured yet rather than showing zeroes.

My client can't see the server at all

Quit and reopen the client after editing its config — most clients only read MCP configuration at startup. Then check the JSON is valid (a trailing comma is the usual culprit) and that the URL is exactly https://cms.contentin.io/mcp-server with no trailing slash. In Claude Code, run /mcp to see the connection status.

Scheduling was rejected because of the time

Times need an explicit UTC offset — 2026-08-04T09:00:00+02:00 or 2026-08-04T07:00:00Z. A bare local time is refused on purpose, because ContentIn can't know your timezone and guessing would publish hours off. Tell your assistant your timezone once and it will handle the format from there.