npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

manus-mcp

v1.0.0

Published

MCP server for Manus API - Create AI tasks and manage webhooks

Readme

Manus MCP

The Universal MCP Server for Manus AI enables you to create AI tasks, manage webhooks, and integrate Manus workflows into any MCP-compatible client. Designed for prompt-first usage with full support for attachments, connectors, and real-time notifications.

Installation

Prerequisites

  • Node.js 18+
  • Set MANUS_MCP_API_KEY in your environment

Get an API key

  • Request your API key from the Manus Dashboard
  • API documentation: https://open.manus.ai/docs
  • Getting started guide: https://open.manus.ai/docs/quickstart

Build locally

cd /path/to/manus-mcp
npm i
npm run build

Setup: Claude Code (CLI)

Use this one-liner (replace with your real API key):

claude mcp add "Manus MCP" -s user -e MANUS_MCP_API_KEY="your-api-key-here" -- npx manus-mcp

To remove:

claude mcp remove "Manus MCP"

Setup: Cursor

Create .cursor/mcp.json in your client (do not commit it here):

{
  "mcpServers": {
    "manus-mcp": {
      "command": "npx",
      "args": ["manus-mcp"],
      "env": { "MANUS_MCP_API_KEY": "your-api-key-here" },
      "autoStart": true
    }
  }
}

Note: This repository does not include .cursor/mcp.json. Configure Cursor via the UI or manually create the file in your client workspace.

Other Clients and Agents

Install via URI or CLI:

code --add-mcp '{"name":"manus-mcp","command":"npx","args":["manus-mcp"],"env":{"MANUS_MCP_API_KEY":"your-api-key-here"}}'

Or add to your VS Code settings JSON:

{
  "mcp.servers": {
    "manus-mcp": {
      "command": "npx",
      "args": ["manus-mcp"],
      "env": { "MANUS_MCP_API_KEY": "your-api-key-here" }
    }
  }
}

Same as VS Code, but use code-insiders command:

code-insiders --add-mcp '{"name":"manus-mcp","command":"npx","args":["manus-mcp"],"env":{"MANUS_MCP_API_KEY":"your-api-key-here"}}'

Add to your Claude Desktop configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "manus-mcp": {
      "command": "npx",
      "args": ["manus-mcp"],
      "env": { "MANUS_MCP_API_KEY": "your-api-key-here" }
    }
  }
}

In LM Studio's MCP settings:

  • Command: npx
  • Args: ["manus-mcp"]
  • Env: MANUS_MCP_API_KEY=your-api-key-here

Add to your Goose configuration:

  • Type: STDIO
  • Command: npx
  • Args: manus-mcp
  • Enabled: true
  • Env: MANUS_MCP_API_KEY=your-api-key-here

Example ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "manus-mcp": {
      "type": "local",
      "command": ["npx", "manus-mcp"],
      "enabled": true,
      "env": { "MANUS_MCP_API_KEY": "your-api-key-here" }
    }
  }
}

Add a new MCP in Qodo Gen and paste the standard JSON config:

{
  "command": "npx",
  "args": ["manus-mcp"],
  "env": { "MANUS_MCP_API_KEY": "your-api-key-here" }
}

Follow the Windsurf MCP integration guide and reuse the standard config:

{
  "manus-mcp": {
    "command": "npx",
    "args": ["manus-mcp"],
    "env": { "MANUS_MCP_API_KEY": "your-api-key-here" }
  }
}

Setup: Codex (TOML)

Add the following to your Codex TOML configuration.

Example (Serena reference):

[mcp_servers.serena]
command = "uvx"
args = ["--from", "git+https://github.com/oraios/serena", "serena", "start-mcp-server", "--context", "codex"]

This server (minimal):

[mcp_servers.manus-mcp]
command = "npx"
args = ["manus-mcp"]
# Optional environment variables:
# MANUS_MCP_API_KEY = "your-api-key-here"
# MCP_NAME = "manus-mcp"

Configuration (Env)

  • MANUS_MCP_API_KEY: Your Manus API key (required)
  • MANUS_MCP_API_BASE_URL: Override the API base URL (default: https://api.manus.ai/v1)
  • MCP_NAME: Server name override (default: manus-mcp)

Available Tools

create_task

Create a new AI task in Manus with custom parameters and optional attachments.

Inputs:

{
  "prompt": "string (required) - The task prompt or instruction for the AI",
  "mode": "string (required) - 'speed' or 'quality'",
  "attachments": "array (optional) - List of attachment objects { filename, url, mime_type, size_bytes }",
  "connectors": "array (optional) - List of connector IDs (e.g., ['gmail', 'notion'])",
  "hide_in_task_list": "boolean (optional) - Hide from webapp task list (default: false)",
  "create_shareable_link": "boolean (optional) - Generate a public shareable link (default: false)"
}

Outputs:

{
  "task_id": "string - Unique task identifier",
  "task_title": "string - Generated task title",
  "task_url": "string - Direct link to the task",
  "shareURL": "string (optional) - Public shareable link if requested"
}

create_webhook

Register a new webhook to receive real-time notifications from Manus.

Inputs:

{
  "url": "string (required) - Webhook endpoint URL",
  "events": "array (optional) - List of event types to subscribe to"
}

Outputs: Webhook registration details including webhook ID and configuration.

delete_webhook

Remove a previously registered webhook by its ID.

Inputs:

{
  "webhook_id": "string (required) - The ID of the webhook to delete"
}

Outputs: Success confirmation or error details.

Example invocation (MCP tool call)

Create a task in speed mode:

{
  "tool": "create_task",
  "arguments": {
    "prompt": "Analyze the quarterly sales data and generate a summary report with key insights",
    "mode": "speed",
    "create_shareable_link": true
  }
}

Create a task with attachments:

{
  "tool": "create_task",
  "arguments": {
    "prompt": "Extract key action items from this meeting transcript",
    "mode": "quality",
    "attachments": [
      {
        "filename": "meeting-notes.pdf",
        "url": "https://example.com/files/meeting-notes.pdf",
        "mime_type": "application/pdf",
        "size_bytes": 245632
      }
    ],
    "connectors": ["gmail", "notion"]
  }
}

Troubleshooting

401 Authentication Error

  • Verify that MANUS_MCP_API_KEY is correctly set in your environment
  • Check that your API key is valid and has not expired
  • Test your API key with a direct curl request:
    curl -H "API_KEY: your-key" https://api.manus.ai/v1/tasks

Node.js Version Error

  • Ensure you're using Node.js 18 or later: node -v
  • Update Node.js if necessary: https://nodejs.org/

Build Issues

  • Clear the build directory: rm -rf build
  • Reinstall dependencies: rm -rf node_modules && npm i
  • Rebuild: npm run build

Testing Local Builds

  • After building, test the server: npx . or node build/index.js
  • Check that the executable is properly created: ls -la build/index.js

Inspecting Publish Artifacts

  • See what would be published: npm pack --dry-run
  • Check the package contents: npm pack && tar -xzf manus-mcp-*.tgz && cat package/package.json

References

  • Manus API Documentation: https://open.manus.ai/docs
  • MCP SDK: https://modelcontextprotocol.io/docs/sdks
  • MCP Architecture: https://modelcontextprotocol.io/docs/learn/architecture
  • MCP Server Concepts: https://modelcontextprotocol.io/docs/learn/server-concepts
  • MCP Server Specification: https://modelcontextprotocol.io/specification/2025-06-18/server/index
  • Manus Quickstart: https://open.manus.ai/docs/quickstart
  • Manus Webhooks: https://open.manus.ai/docs/webhooks/overview
  • Manus Connectors: https://open.manus.ai/docs/connectors/overview

Name Consistency & Troubleshooting

Always use CANONICAL_ID (manus-mcp) for identifiers and keys. Use CANONICAL_DISPLAY (Manus MCP) only for UI labels. Do not mix legacy keys after registration.

Consistency Matrix

| Context | Value | |-------------------------------|---------------| | npm package name | manus-mcp | | Binary name | manus-mcp | | MCP server name (SDK metadata)| manus-mcp | | Env default MCP_NAME | manus-mcp | | Client registry key | manus-mcp | | UI label | Manus MCP |

Conflict Cleanup

  • Remove any stale keys (e.g., old display names like "Manus") and re-add with manus-mcp only
  • Ensure global .mcp.json or client registries only use manus-mcp for keys
  • Cursor: Configure in the UI; this project intentionally omits .cursor/mcp.json

Example

Correct:

{
  "mcpServers": {
    "manus-mcp": {
      "command": "npx",
      "args": ["manus-mcp"]
    }
  }
}

Incorrect:

{
  "mcpServers": {
    "Manus": {  // Wrong: will conflict with "manus-mcp"
      "command": "npx",
      "args": ["manus-mcp"]
    }
  }
}

License

MIT