Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
doc2mcp avatar

Manus

  • 2 repo stars
  • Updated July 11, 2026
  • doc2mcp/doc2mcp

manus is an MCP server that lets agents query manus documentation hosted on doc2mcp via token-authenticated streamable HTTP.

About

Manus MCP exposes manus project documentation through the Model Context Protocol using doc2mcp’s generated remote server pattern, aimed at developers who want their coding agent to treat manus docs as first-class context. After you publish documentation on doc2mcp for manus, adding this MCP is the low-friction way to align agent suggestions with your guides, configuration notes, and API descriptions. The integration is intentionally simple: one streamable-http URL, one Bearer token from Connect, and standard MCP client configuration. Reach for it during feature work, when validating scope against written manus requirements, or when supporting yourself in chat-driven debugging—not when you need database queries or CI triggers. Security hygiene matters because the token grants documentation API access; rotate it if exposed. This is documentation retrieval infrastructure for agents, complementary to manus application code and separate from generic web search skills.

  • Manus-titled MCP server generated by doc2mcp with hosted streamable-http API
  • Bearer MCP token from manus project Connect tab—secret, required, password-equivalent
  • Brings manus documentation into Claude Code, Cursor, Codex, or Windsurf MCP tool lists
  • Eliminates ad-hoc doc paste workflows for manus-specific questions during sprints
  • Source generator at github.com/doc2mcp/doc2mcp with manus remote URL on doc2mcp.site

Manus by the numbers

  • Data as of Jul 12, 2026 (Skillselion catalog sync)
terminal
claude mcp add --transport http manus https://doc2mcp.site/api/mcp/221536c8-fc67-48b8-a177-b04b58d6b268/mcp --header "Authorization: Bearer YOUR_TOKEN"

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars2
TransportHTTP
AuthRequired
Last updatedJuly 11, 2026
Repositorydoc2mcp/doc2mcp

What it does

Register the manus doc2mcp documentation MCP so your agent uses manus official docs when implementing features and integrations.

Who is it for?

Best when you're documenting manus on doc2mcp and want reliable doc-backed answers inside AI-assisted coding workflows.

Skip if: Skip if you seek manus production monitoring, or teams without doc2mcp-hosted manus docs and MCP credentials.

What you get

Adding manus MCP with your Connect-tab token grounds agent replies in manus documentation while you develop and integrate.

  • Registered manus documentation MCP in your agent environment
  • Doc-grounded manus answers without manual copy-paste from the doc2mcp site
  • Aligned doc2mcp-generated tool surface for manus documentation

By the numbers

  • 1 streamable-http remote on doc2mcp.site
  • 1 required secret Authorization header
  • Server version 1.0.1780872068 in metadata
README.md

doc2mcp — MCP Registry manifest

This repository is not the doc2mcp product. It is the small, GitHub‑OIDC‑authenticated publishing manifest for the official Model Context Protocol Registry.

What Where
MCP Registry entry https://registry.modelcontextprotocol.io/v0.1/servers?search=doc2mcp
Live product https://doc2mcp.site
Registry namespace io.github.doc2mcp/doc2mcp
Current version 1.0.1

Why a separate repo?

The MCP Registry uses GitHub OIDC to claim a namespace. Whichever GitHub org or user runs mcp-publisher publish from a workflow gets exclusive publishing rights to io.github.<that-org>/*.

Since we want the public, brandable namespace io.github.doc2mcp/* (instead of io.github.gautammanak1/*), the publish workflow must run inside the doc2mcp GitHub organization. This repository holds only the publishing manifest and workflow — nothing else.

gautammanak1/doc2mcp   →  product code, Vercel deploy, docs site
doc2mcp/doc2mcp        →  this repo. server.json + publish workflow

What clients should use

To connect to doc2mcp from Cursor, Claude Desktop, VS Code, Windsurf, the OpenAI Agents SDK, etc., point your MCP host at the remote URL in server.json:

{
  "type": "streamable-http",
  "url": "https://doc2mcp.site/api/mcp/{project_id}/mcp",
  "headers": { "Authorization": "Bearer <your project MCP token>" }
}

Get your project_id and Bearer token from

Publishing flow

Pushing a vX.Y.Z tag to main triggers .github/workflows/publish-mcp.yml, which:

  1. Updates the version field in server.json to match the tag.
  2. Installs the official mcp-publisher CLI.
  3. Authenticates via GitHub OIDC (id-token: write).
  4. Publishes the manifest to the registry.

To cut a new version:

# from this repo
git tag v1.0.2
git push origin v1.0.2

The workflow validates against the upstream JSON Schema before publish, so a bad description length or missing required field will fail loudly with a clear error.

License

The manifest in this repo is published under the MIT License. The doc2mcp product itself is licensed in its main repository.

Recommended MCP Servers

How it compares

Doc2mcp documentation remote MCP, not the Manus agent product itself or a generic skills.sh skill.

FAQ

Who is Manus MCP for?

Developers and small teams maintaining Manus documentation on doc2mcp who use MCP-capable coding agents.

When should I use Manus MCP?

Use it during build and docs-driven integration work when answers should come from Manus official doc2mcp content.

How do I add Manus MCP to my agent?

Copy the Manus project MCP Bearer token from doc2mcp Connect, configure the remote streamable-http URL, and set the Authorization header to Bearer plus the token.

Developer Toolsdocsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.