
Connect Claude, ChatGPT, Cursor, VS Code or any MCP client to Moderation API, and let your agent work your queues, authors and policies.
Most moderation work happens in the dashboard, one item at a time. Your AI agent could do the first pass, but it had no way into your account.
Today, we're launching the Moderation API MCP server at https://mcp.moderationapi.com/mcp. It is hosted, so there is nothing to install, and you don't need an API key: you sign in to Moderation API in the browser when it opens.
Setup steps for every client are on the MCP server page in the dashboard, under Configure → MCP server.
Claude and Claude Desktop. Moderation API is in the Claude connectors directory. Open Moderation API in the directory, connect it and sign in.
Claude Code. Run claude mcp add --transport http moderation-api https://mcp.moderationapi.com/mcp, restart Claude Code, then type /mcp and sign in. Or install the plugin, which adds the MCP server and the setup skill together: /plugin marketplace add moderation-api/skills, then /plugin install moderation-api@moderation-api.
ChatGPT. Turn on Developer mode under Settings → Apps & Connectors → Advanced settings. Back in Apps & Connectors, click Create, enter the name Moderation API, paste the URL and set Authentication to OAuth. You need a ChatGPT plan that has developer mode.
Cursor. Click Add to Cursor on the MCP server page, or add the URL to .cursor/mcp.json. Then click Connect next to moderation-api in Cursor Settings → MCP.
VS Code. Click Add to VS Code on the MCP server page, or run code --add-mcp with the URL. Start the server and sign in when the browser opens.
Other clients. Add a remote MCP server with the URL.
The first time, your browser opens: sign in, choose an organization and approve the connection. Owners, admins and developers can connect.
Test content. "Send three test messages to Moderation API, one clean, one spam and one with an insult, and show me what got flagged and why."
Triage the queue. "Go through my review queue and show me the items you are not sure about." It can resolve up to 100 items at a time.
Check an author. "Check user history and suspend them if it's a pattern."
Tune a policy from examples. Give it the messages that got through and the ones flagged by mistake. It tests them without storing anything, then adjusts thresholds or wordlists.
Respond to an incident. Find a scam raid, block the authors and add the domains to a blocklist.
Report. "How did moderation go this week? Which policy flags the most?"
The server ships these as ready-made prompts: triage-queue, check-author, tune-policy, incident-response and moderation-report. More examples are in the docs.
Already moderating content? Your coding agent can review the integration you have and fix what's wrong. Install the Moderation API skill with npx skills add moderation-api/skills (the Claude Code plugin above includes it), then ask your agent to "review my Moderation API integration and fix any mistakes".
The skill checks your code against the mistakes we see most often:
Acting on the wrong field. Reading evaluation.flagged instead of recommendation.action, which skips your rules, thresholds and review routing.
No handling for review. Treating review the same as allow or reject.
Gaps in coverage. Moderating text only, and missing images, profile names, bios and uploads.
Missing webhooks. Without them, your app never hears what a moderator decided later, or that an author was blocked.
Unsafe webhook handling. Not checking the signature on the raw body, or handling a retried event twice.
Missing context. No authorId, conversationId or stable contentId, so author history, conversation context and edits are lost.
Risky calls. Calling from the browser, no timeout, or blocking users when the API can't be reached instead of failing open.
Your agent asks before each change and never asks for your keys in the chat. Starting from scratch? Ask it to "set up Moderation API" and it writes the integration for you. Read more about the skill.