Moderation API

com.moderationapiPublished by moderationapi.comOfficial publisherv1.0.1Updated Oct 29, 2026

Run your Moderation API account: review queues, authors, policies, wordlists and analytics.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server that lets an assistant operate a Moderation API account: review queues, authors, policies, wordlists, webhooks and analytics.

What you can do
  • Submit content for moderation and allow or reject it, with or without storing it
  • List, resolve and unresolve review queue items in bulk and read queue statistics
  • Look up, create, update, block, suspend and unblock authors
  • Read and change channels, policies, wordlists and their words
  • Run moderation actions and manage projects, API keys and webhooks
  • Read analytics on flagged policies, authors, channels and volumes over time
When to use it
Useful when you already run moderation through Moderation API and want an agent to do a first pass on review queues, investigate suspicious authors, tune policies from examples, handle incident bursts, or produce moderation reports without opening the dashboard.
Requirements
Remote Streamable HTTP endpoint at mcp.moderationapi.com/mcp; nothing to install. Needs a Moderation API account with the Owner, Admin or Developer role and OAuth sign-in in a browser, or an API key sent as an Authorization Bearer header for clients without a browser.
Before you install
The connection can change and delete data: resolving queue items, blocking or suspending authors, editing policies and wordlists, creating API keys and webhooks. Actions are recorded under your name as reviewer. Each connection gets its own API key; an organization key reaches every project it is allowed to. Delete the key to end access.

Installation

In SourceWeft

  1. Open Moderation API in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.moderationapi%2Fmoderation-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "moderation-api": {
      "type": "http",
      "url": "https://mcp.moderationapi.com/mcp"
    }
  }
}

README

[Moderation API]

Moderation API MCP Server

Let AI agents run your Moderation API account: work through review queues, investigate authors, tune policies and wordlists, respond to incidents and report on how moderation is going.

This is a hosted (remote) Model Context Protocol server. Connect Claude, Cursor or any other MCP client to:

https://mcp.moderationapi.com/mcp

There is nothing to install. The server has one tool for each endpoint of the REST API, and it calls the same API as your code, so rate limits, quotas and request logs work the same way.

What your agent can do

  • Triage the review queue. "Go through today's unresolved items, reject the obvious spam, and show me the 5 you're unsure about." The agent does the first pass; you make the judgment calls.
  • Investigate an author. "Is user 8812 a bad actor? Check their history and suspend them if it's a pattern."
  • Tune policies from real examples. "These 10 comments got flagged but are fine, and these 3 got through. Fix it." The agent tests the examples without storing them, finds the thresholds or wordlist entries that separate them, and updates the channel.
  • Respond to incidents. "There's a raid of crypto scam posts in the last hour. Find them, block the authors, and add the domains to the blocklist."
  • Set up moderation without the dashboard. "Set up moderation for our new marketplace: a channel for listings, one for messages, and a webhook to our endpoint." Then send test content to check it.
  • Report and audit. "How did moderation go this month?" Queue stats, actions and author trends turned into a summary.
  • Combine with your other tools. A daily queue digest in Slack, an issue when a policy keeps misfiring, a draft reply to the user whose post was removed.

The server also ships prompts (recipes) for these jobs: triage-queue, check-author, tune-policy, incident-response and moderation-report. More example prompts: What your agent can do.

Tools

AreaWhat the tools do
ContentSubmit content and read the result, with or without storing it; allow or reject content
Review queuesList queues and items, resolve and unresolve items one by one or up to 100 at a time, queue statistics
AuthorsList, look up, create and update authors; block, suspend and unblock them
ActionsList and run moderation actions on content and authors; create and change actions
PoliciesRead and change channels and their policies; create and change wordlists and their words
AnalyticsSummary, most flagged policies and authors, numbers per channel, volumes over time, automation
ProjectsList, create, change and duplicate projects; create API keys
WebhooksList, create and change webhooks
FeedbackSend a feature request to the Moderation API team

Read-only tools are marked as read-only, so your agent can run them without asking. Tools that change or delete data are marked as such, and most agents ask you before they run them.

Setup

You need a Moderation API account with the Owner, Admin or Developer role. Sign up free.

Claude Code

bash
claude mcp add --transport http moderation-api https://mcp.moderationapi.com/mcp

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

Claude and Claude Desktop

Open Settings → Connectors → Add custom connector, and enter https://mcp.moderationapi.com/mcp.

Cursor

Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects:

json
{  "mcpServers": {    "moderation-api": {      "url": "https://mcp.moderationapi.com/mcp"    }  }}

Other clients

Add a remote MCP server with the URL https://mcp.moderationapi.com/mcp and the Streamable HTTP transport.

Sign in

The first time your 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.

The agent can reach the projects that you can reach. Each connection gets its own API key, shown on the API keys page and 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:

bash
claude mcp add --transport http moderation-api https://mcp.moderationapi.com/mcp \  --header "Authorization: Bearer $MODAPI_SECRET_KEY"

A project key reaches one project. An organization key reaches the projects you allow it to.

Projects

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

Other tools for agents

  • Setup skill: lets a coding agent add Moderation API to your app's code. npx skills add moderation-api/skills
  • CLI: sign in, create a project and write API keys from the terminal. modapi init

See Build with AI agents.

Links

License

MIT

Source: README.md at commit 8273d25

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts