Connect Claude.ai to ContentForge

Claude.ai connects to ContentForge as a custom connector. You sign in with your normal ContentForge login, so you don't need an API key.

Before you start

• You need a Claude plan that lets you add custom connectors. On a team or company workspace, the workspace owner may need to allow or add it first.
• Open ContentForge on its main address, not one of your client domains. Agency sign-in only works there.

Steps

1. In ContentForge, go to Settings → API & MCP.
2. In the Connect your AI card, click Copy next to MCP server URL. It ends in /api/mcp.
3. In Claude.ai, open Settings → Connectors and choose Add custom connector. (The menu names can change. Look for your connector or integration settings.)
4. Give it a name, such as "ContentForge", paste the URL and add it. Leave any advanced or client ID fields empty.
5. Click Connect on the new connector. A ContentForge page opens.
6. If you're signed out, sign in with your ContentForge email and password. You come straight back to the connect page.
7. The page is called Connect Claude to ContentForge (it shows the name the app gave itself, usually "Claude"). On it:
   • Under Account, pick your agency. It reads "(agency — every client you can reach)".
   • Under What Claude may do, tick what you want. Read your sites, pages, posts and reports is always on. Change drafts lets it edit and create things. Publish: put changes live on the site lets it publish. Untick Publish if you'd rather publish yourself. See MCP permissions explained.
   • Check the line "After you allow it, you go back to …". It should be Claude's own address. Only allow apps you set up yourself.
8. Click Allow. You're sent back to Claude.ai and the connector shows as connected.

Check it worked

1. Start a new chat. Make sure ContentForge is switched on in the chat's tools or connectors menu.
2. Ask: "List my clients in ContentForge."
3. Claude may ask you to allow the tool the first time. Allow it. You should see your clients.
4. In ContentForge, Settings → API & MCP → Connected apps (sign-in) now lists the app as Active, with when it was last used.

Good to know

• The connection acts as you. It only reaches the clients and tools your role allows.
• Sign-in stays connected on its own. If you don't use it for 30 days it expires and you click Connect again.
• To change what it may do (for example, add Publish), disconnect it and connect again with the new choices.
• To stop it, click Disconnect under Connected apps (sign-in), or remove the connector in Claude.ai.
• Connectors you add in Claude.ai also show in Claude Desktop when you're signed in to the same Claude account.
• If ContentForge gets new tools, start a new chat. If they still don't show, disconnect and connect again. See MCP troubleshooting.