A
licenseNot graded
qualityD
maintenanceTurns any CLI tool or REST API into an MCP server for Claude, enabling Claude to use git, databases, or any API through natural language.
MIT
Manus MCP
by 0-SOFT
Related Servers
Alternatives to Manus MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for orchestrating coding tasks with frontier-model planning and local execution, enabling manifest validation, plan submission, status checks, cancellation, and report retrieval through Claude Code.6MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.5 npmMIT
- AlicenseAqualityBmaintenanceLocal MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.3MIT
- AlicenseAqualityAmaintenanceMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.31801 npm920MIT
- FlicenseNot gradedqualityCmaintenanceA remote MCP server that wraps the Manus API to expose a generate_image tool, enabling Claude to request image generation via Manus.-
TDQS
A3.7/5.0
Scored across 36 tools
Disambiguation5/5
Each tool targets a distinct resource and action within well-defined domains (agent, file, task, webhook, website, etc.). There is no overlap in purpose; for example, manus_task_create, manus_task_send_message, and manus_task_stop are clearly different operations.
Naming Consistency5/5
All tools follow a consistent 'manus_<domain>_<action>' pattern (e.g., manus_agent_list, manus_file_upload, manus_task_wait). Even compound names like manus_task_list_messages adhere to this structure, making tool names predictable and easy to parse.
Tool Count4/5
With 36 tools, the server covers a broad set of features (agents, browsers, connectors, files, projects, skills, tasks, usage, webhooks, websites). While this is on the higher side, each tool is justified by the complexity of the platform and no obvious bloat is present.
Completeness4/5
The tool surface provides CRUD-like coverage for most domains: task management includes create, read, list, update, delete, stop, wait, confirm; files have create, upload, detail, delete; webhooks have full lifecycle. Minor gaps exist (no file update or project update), but these are acceptable given the domain.
Maintenance
ActivityInactive
ResponsivenessNo issues