Connect Claude, Cursor or another AI app to Publedia with MCP

Publedia runs an MCP server, so an AI app that speaks the Model Context Protocol can work with your workspace directly. Depending on what you allow, it can look at your posts, calendar, analytics (beta), inbox (beta) and channels, create and edit drafts, or schedule and publish for you.

The app learns what it can do from the server when it connects, so what follows is the setup and the kinds of requests that work, not a fixed list of actions.

Before you start

• You need to be an admin of the workspace. Only admins can create API keys.
• Decide how much the app should be allowed to do. A key keeps its access until you revoke it, and the app does not ask you again before using it.

1. Create a key for your app

1. Open Settings and choose Developers under your workspace.
2. In Connect an AI app, pick your app: Claude Code, Claude Desktop, Cursor, VS Code, or Other for any app that can call an HTTP MCP server. The key is named after the app you pick.
3. Choose one of the three presets:

4. Replying to comments is a separate choice: tick Also reply to comments only if the app should answer comments for you. It is off by default. No key can ever send direct messages.
5. Select Create key for your app, and copy the key when it is shown. It is shown once. If you lose it, revoke it and create another.

A key that cannot publish can still schedule, but only for a time at least 15 minutes ahead, so there is always a window to catch a post in the calendar before it goes out.

2. Copy the setup for your app

After you create the key, the same screen shows a ready-made setup for the app you picked, with your workspace's server address already in it. Copy it from there. For Claude Code, the setup reads the key with read -rs MCP_API_KEY, so the key is typed at a hidden prompt and stays out of your shell history.

Every setup comes down to the same two things, if your app asks for them separately:

• Server address: your Publedia API address followed by /mcp.
• Authentication: a header named Authorization with the value Bearer followed by a space and your key.

For where each app keeps its MCP settings, see its own documentation: Claude Code adds a server with the claude mcp add command, and Cursor reads it from an mcp.json file. Restart the app or reload its MCP servers after adding one.

claude.ai and ChatGPT

Custom connectors in claude.ai and in ChatGPT sign in with OAuth. Publedia's server uses API keys, so these two cannot connect today.

3. Check the connection

Ask your app something only Publedia would know, such as "Which of my Publedia posts are scheduled for tomorrow?" If it answers with your posts, you are connected. Most apps also list the connected servers and their tools in their settings.

Ready-made prompts

The server offers three ready prompts, which apps that support MCP prompts show in their prompt or command menu:

• Review performance: a look at how recent posts did and what stood out.
• Plan posts: a set of post ideas for the coming days, based on your channels and what you give it.
• Triage the inbox: new comments sorted by what needs an answer first.

Prompts to try

Ask in plain language; the app picks the right action.

• "Which Instagram posts from the last 30 days got the most comments? Draft three follow-ups." (needs Drafts)
• "What failed this week, and why?"
• "Plan next week's posts from this blog post: [paste or link it]." (needs Drafts)
• "Is any channel in my workspace waiting to be reconnected?"
• "Retry the Instagram post that failed this morning." (needs Full control)

With the Drafts preset, everything the app writes lands as a draft in Publedia, where you check each network's version and preview before scheduling it yourself. That is the safest way to start.

What the app can and cannot do

• A key reaches one workspace. For another workspace, create a key there.
• A key never does more than its preset allows, and never more than the role of the admin who created it.
• Comments written by people outside your workspace reach the app marked as untrusted, so an instruction hidden in a comment is not treated as yours.
• Each change made with a key is recorded against that key.
• Requests are rate limited per workspace. An app that sends too many in a short time is asked to wait and try again.

Revoke a key

In Settings, Developers, revoke the key beside its name and confirm. Every request made with it is refused from then on, and any app still holding it stops working. To reconnect that app, create a new key and update its setup.

If the connection fails

• "Send a workspace API key as a bearer token": the Authorization header is missing, or does not start with Bearer and a space.
• "That API key is not valid": the key was revoked, has expired or was mistyped. Create a new one.
• "This workspace does not accept external clients": AI app access is turned off for the workspace. An admin can turn it back on in Settings, Developers.
• "This workspace has reached its request limit": wait a moment and try again.