Manus MCP Server

MCP server exposing the full Manus API v2 surface to Claude Code

Local serverstdioPython

What is the Manus MCP server?

Most developer tooling work still happens through a UI a human drives. Manus MCP server moves it into the conversation instead. MCP server exposing the full Manus API v2 surface to Claude Code.

The short version

An MCP server that gives Claude Code full programmatic control over Manus.im through the official Manus API v2. Implements all 30 documented endpoints, 3 composite tools for common workflows, and a local webhook receiver with RSA-SHA256 signature verification.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • manus_webhook_events_list — list received events with filters
  • manus_webhook_events_get — fetch an event by event_id
  • manus_webhook_events_clear — delete received events
  • Category — Tools

Getting it running

Installation goes through your MCP client rather than a global install: point it at manus-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: MANUS_API_KEY, MANUS_BASE_URL, MANUS_WEBHOOK_PUBLIC_URL, MANUS_WEBHOOK_HOST, MANUS_WEBHOOK_DB_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Manus's toolset — manus_webhook_events_list, manus_webhook_events_get, manus_webhook_events_clear and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Manus MCP Contributors; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Manus's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
manus_webhook_events_listlist received events with filters.
manus_webhook_events_getfetch an event by event_id.
manus_webhook_events_cleardelete received events.
CategoryTools

How to install the Manus MCP server

{
  "mcpServers": {
    "manus-1": {
      "command": "uvx",
      "args": ["manus-mcp"],
      "env": {
        "MANUS_API_KEY": "your-value",
        "MANUS_BASE_URL": "your-value",
        "MANUS_WEBHOOK_PUBLIC_URL": "your-value",
        "MANUS_WEBHOOK_HOST": "your-value",
        "MANUS_WEBHOOK_DB_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MANUS_API_KEYCredential the server authenticates with.Yes
MANUS_BASE_URLEndpoint or connection string the server talks to.Yes
MANUS_WEBHOOK_PUBLIC_URLEndpoint or connection string the server talks to.Yes
MANUS_WEBHOOK_HOSTEndpoint or connection string the server talks to.Optional
MANUS_WEBHOOK_DB_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Manus to manus webhook events list.
  • Use Manus to manus webhook events get.
  • Use Manus to manus webhook events clear.

Frequently asked questions

It connects Manus to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (manus_webhook_events_list, manus_webhook_events_get, manus_webhook_events_clear, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Manus directly.