Connect ContentIn to Claude, ChatGPT, Cursor and your other AI tools

2. Add the server to your client

Connect with one click

One remote server, the same URL for every client. There's no key to copy and no header to set: you paste the URL, sign in with ContentIn, and you're connected.

Server URL

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

Transport

Streamable HTTP

Sign-in

ContentIn (OAuth), no key needed

Permissions

read, write, publish

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

claude mcp add --transport http contentin https://mcp.contentin.io/mcp-server

{
  "mcpServers": {
    "contentin": {
      "url": "https://mcp.contentin.io/mcp-server"
    }
  }
}

{
  "servers": {
    "contentin": {
      "type": "http",
      "url": "https://mcp.contentin.io/mcp-server"
    }
  }
}

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

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

3. What you can do

Eleven 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.”
• “Attach these two screenshots to the post you just drafted, then schedule it for Tuesday 9am.”
• “Who engaged with my posts this month, sorted by ICP fit, and which post pulled them in?”
• “Pull the comments I left last week so I can follow up on the ones that got replies.”

4. What the server will and won't do

5. Troubleshooting

The ContentIn sign-in page doesn't open

Check the URL is exactly https://mcp.contentin.io/mcp-server, with no trailing slash and nothing after it. Some clients only start the sign-in when you trigger it: in Claude Code run /mcp, select contentin and choose Authenticate; in Cursor and VS Code use the sign-in prompt on the server entry. If a pop-up blocker is on, allow pop-ups for your client and try again.

I connected the wrong profile

Revoke the connection in ContentIn under Profiles → Connections, then reconnect from your client and pick the right profile on the sign-in page. To work with two profiles, add the server twice under different names and approve each one for a different profile.

My client asks me to approve again when it publishes

That's expected the first time. Publishing to LinkedIn is a separate permission: your client asks for it on the first publish, you approve it on the ContentIn page, and it isn't asked again for that connection.

"Invalid key" when using an API key

Re-copy the key in ContentIn: open app.contentin.io/profiles, switch to the Connections tab and find "Connect AI clients" under your connected LinkedIn profile. 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.

"Plan too low" or "Requires Pro" when the tools are called

The MCP server is included from the ContentIn Growth plan, and the server checks your plan live on every call. list_leads and list_my_comments need Pro and return an upgrade hint on Growth; every other tool works on Growth. If you've just upgraded, the tools start working on the next call — no need to reconnect or restart your client. If you're not on Growth yet, start a trial and the same connection works the moment the plan is active.

I hit the rate limit

Each connection 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 you picked when you connected 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 — some 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://mcp.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.