Skip to main content
The Moderation API MCP server lets an AI agent work with your account: go through review queues, look up authors, change policies and wordlists, read analytics and more. It is hosted at:
The server has one tool for each endpoint of the REST API. To add moderation to the code of your app, use the setup skill instead.

Connect your agent

Or install the plugin, which adds the MCP server and the setup skill together.

Sign in

The first time the agent uses the server, your browser opens:
  1. Sign in with your Moderation API account.
  2. Pick the organization the agent can use.
  3. Approve the connection.
You need the Owner, Admin or Developer role in the organization. The agent can reach the projects that you can reach. Each connection gets its own API key. It shows on the API keys page, named after the app and your email. Delete the key to end the connection. When the agent resolves queue items or runs actions, the review queue shows you as the reviewer.

Without a browser

Agents that cannot open a browser, for example in CI, can send an API key instead:
A project key reaches one project. An organization key reaches the projects you allow it to. See Authentication.

Projects

Tools that work on content in a project take an optional projectId. You can give the project ID or its name. When the agent leaves it out and the key reaches more than one project, the tool returns the projects to choose from.

What the tools can do

Tools that only read data are marked as read-only, so your agent can run them without asking you. Tools that change or delete data are marked as such, and most agents ask you before they run them. See What your agent can do for prompts to start with.

Limits

The MCP server calls the same API as your code. Rate limits, quotas and request logs work the same way.