MCP integration

AI Detector MCP for Claude and Codex

Analyze text inside your assistant through a secure Streamable HTTP MCP connection.

Codex MCP configuration
export DETECTING_AI_API_KEY="YOUR_API_KEY"

[mcp_servers.detecting_ai]
url = "https://api.detecting-ai.com/api/mcp"
bearer_token_env_var = "DETECTING_AI_API_KEY"
tool_timeout_sec = 180

What an AI Detector MCP server does

An AI Detector MCP server gives a compatible assistant permission to call a dedicated detection tool. The assistant sends only the text selected for analysis, receives structured detector output, and can explain the result in the context of the current task.

  • Stay in the active conversationCheck a draft, submission, or document without moving text between separate browser tools.
  • Use structured detector outputThe tool returns the detector version, processed word count, and detailed analysis for the assistant to interpret.
  • Keep one subscription balanceMCP calls use the same detector word allowance as the Detecting AI REST API.
  • Control when analysis runsThe assistant calls the detector only when the user requests analysis or approves a workflow that includes it.
Detecting AI dashboard with the AI Detection tool selected

From prompt to detector result

When a user asks whether text contains AI-writing signals, the client selects the Detecting AI tool and sends the supplied passage. The MCP server validates the API key and detector quota, runs the selected detector version, records usage, and returns structured output to the client.

Available MCP tool

detect_ai_text: Analyzes text for AI-writing signals and returns detailed detector output.

InputTypeStatusDescription
textstringRequiredThe passage or document section to analyze.
versionv1 | v2 | v3OptionalDetector version. The default is v3.

Compatible MCP clients

Connect through Streamable HTTP with an Authorization bearer header. Client support and configuration formats can vary by version.

Claude CodeAdd the remote HTTP server from the command line.
CodexReference the endpoint and API key environment variable in config.toml.
Claude DesktopUse a remote MCP configuration supported by your client version.
Other agentsConnect any client that supports Streamable HTTP and bearer headers.

Where AI Detector MCP fits

MCP works best when the assistant needs a focused external tool as part of a user-controlled workflow.

Editorial review

Ask an assistant to screen an article draft, summarize detector signals, and identify passages that need human review.

Education workflows

Review submitted writing inside an approved academic workflow while treating detector output as evidence for further review, not proof.

Content operations

Add detector checks to agent-assisted moderation, intake, or quality assurance processes without creating a separate integration layer.

Connect the detector to your assistant

Create a Detecting AI API key, store it outside the project, and add the public MCP endpoint to your client. The server authenticates with a bearer token.

Public MCP endpoint
https://api.detecting-ai.com/api/mcp
Claude Code setup
claude mcp add --transport http --scope user \
  --header "Authorization: Bearer YOUR_API_KEY" \
  detecting-ai https://api.detecting-ai.com/api/mcp

AI Detector MCP questions

What is an AI Detector MCP server?

It is a remote Model Context Protocol server that lets compatible AI clients call a dedicated text detection tool with structured inputs and outputs.

Does it work with Claude and Codex?

Yes. The server uses Streamable HTTP and bearer authentication, which can be configured in Claude Code, Codex, and other compatible MCP clients.

What does the detector tool return?

It returns detailed detector analysis, the selected detector version, and the number of processed words.

Is an AI detection result proof of authorship?

No. Detection scores are probabilistic signals. They should be combined with context, policy, and human review before decisions are made.

How is MCP usage billed?

Successful detector calls use words from the same Detecting AI API subscription and detector balance used by REST requests.

Use AI Detector from your AI client

Create an API key, connect the public MCP endpoint, and keep control of every tool call from the active conversation.