Skip to main content

Custom MCP connector (any MCP client)

Connect ContentMonk to any MCP-compatible AI client - Cursor, VS Code, or your own - using the ContentMonk MCP server URL and secure OAuth sign-in.

Written by Stefan Zorbic

ContentMonk ships a Model Context Protocol (MCP) server, so any MCP-compatible AI client can securely act on your workspace - check AI-answer visibility, research keywords, produce and publish content, and manage your knowledge base, in a conversation.

Using Claude or ChatGPT? Follow the dedicated guides instead - they're one-click: ContentMonk connector for Claude and for ChatGPT. Use this article for any other MCP client.

What it is

The ContentMonk connector is an MCP server that gives your AI client secure, permissioned access to your workspace. It acts on your behalf and only sees the data and actions your workspace role allows.

Requirements

  • A ContentMonk account with a workspace (any plan). Plan quotas apply (content generation, keyword research, etc.).

  • An MCP-compatible client (for example Cursor, VS Code, or a custom MCP client).

  • Your role sets what the connector can do: Viewer (read only), Editor (read + create/edit content), Admin (also workspace settings).

  • Some tools need extra setup: publishing needs a connected CMS (WordPress or Webflow); AEO data needs tracked prompts; Search Console suggestions need a connected Google Search Console.

How to connect

  1. In your MCP client, add a new custom MCP server with this URL: https://api.contentmonk.io/api/mcp

  2. Start the connection. You'll be sent to ContentMonk's secure sign-in (OAuth, powered by WorkOS).

  3. Sign in and, on the consent screen, click Connect to authorize access to your workspace.

  4. Your client can now use ContentMonk tools. You can revoke access anytime from your ContentMonk workspace settings.

What you can do

  • AI visibility / AEO - overall and per-model visibility (ChatGPT, Claude, Google AI Overviews, Perplexity), cited sources, tracked prompts, and competitor tracking.

  • Keyword research & rank tracker - research keywords, add them to ideas, track rankings, and see SERP/competitor positions.

  • Content production - create a brief, generate the article, edit it, and publish or schedule to a connected CMS.

  • Social repurposing - turn an article into social posts.

  • Knowledge base - add and search documents that ground your content.

  • Comments - add and read comments on content editorials.

  • Settings & usage - read workspace settings and check your plan usage/quota.

Limits

The connector allows up to 240 requests per minute. Metered actions (content generation, keyword research, etc.) still count against your plan.

Troubleshooting

  • Nothing happens after "Connect": make sure you completed the consent screen (clicked Connect after signing in). Retry the connection.

  • Asked to sign in again / 401 errors: your session expired or access was revoked - reconnect and re-authorize.

  • "Quota exceeded" (QUOTA_EXCEEDED): you've hit a plan limit - upgrade or wait for the quota to reset.

  • A brief or article seems to hang: long jobs run in the background - ask your client to check status in a moment rather than re-running.

  • Rate limited / too many requests: slow down; the limit is 240 requests per minute.

  • Wrong workspace: the connector resolves to the account that authorized it - list your workspaces first and confirm you're acting on the intended one before any write.

Support

Questions or issues? Email us at [email protected].

Did this answer your question?