mooteam-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Moo.team MCP
Read Moo.team task context from your AI assistant through the HTTPS API. No browser automation, open tabs or background browser session is required.
Русский: передайте ассистенту ссылку или ID задачи. Сервер получает описание, комментарии с авторами и вложения напрямую по API. Он ничего не записывает в Moo.team.
This is an independent community integration, not an official Moo.team product.
What it does
Reads task description, participants, workflow status, parent reference and checklist.
Preserves comment authors, timestamps, chronology and reply relationships.
Adds user-confirmed participant roles from an optional local directory.
Separates human discussion from optional activity history.
Associates files with their task description or specific comment.
Searches task titles/descriptions by project, assignee and lifecycle status.
Reads parents, subtasks and task links with their discussion source.
Compares reads using a bounded gzip history of fingerprints, without storing task bodies.
Updates user-confirmed roles through MCP in a local directory.
Reads images, PDF text/page images, DOCX/XLSX/PPTX text, ZIP listings and text members.
Reports incomplete pagination, unsupported formats and truncated extraction.
Accepts old
app.moo.teamlinks, newnew-app.moo.teamtask links and numeric IDs.
Related MCP server: Gatehouse
Install
Requires Node.js 22.17 or newer.
npm install -g mooteam-mcpCreate a local configuration file outside your repositories:
Windows:
%USERPROFILE%\.config\mooteam-mcp\config.jsonmacOS/Linux:
~/.config/mooteam-mcp/config.json
{
"token": "YOUR_MOOTEAM_BEARER_TOKEN",
"company": "YOUR_X_MT_COMPANY_VALUE"
}Use your existing Moo.team API token and the X-MT-Company value for your workspace.
The company value is the API header value; do not assume it equals a workspace URL ID.
Environment variables can be used instead; see configuration.
mooteam-mcp --checkConnect to Codex
codex mcp add mooteam -- mooteam-mcpOpen a new assistant session after changing the MCP configuration.
On Windows, if the host cannot resolve the npm command shim, use the absolute
node.exe path and the installed package's dist/cli.js; see configuration.
Other stdio MCP clients can launch mooteam-mcp with no arguments.
Example
Ask your assistant:
Read task 12345, distinguish each person's comments, and inspect the attached screenshots.
The assistant calls get_task_context and then read_attachment for relevant files.
Listing an attachment does not mean its contents have been read.
Tool | Purpose |
| Task details, attributed comments, file manifest and changes since last read |
| Read a file belonging to that task or its visible comments |
| Compare current data with the last local baseline |
| Read parents, subtasks and tasks linked in discussion |
| Search titles/descriptions with bounded collection scanning |
| Discover accessible project names and IDs |
| Resolve people and their local roles |
| Save an explicitly supplied role locally |
Boundaries
All Moo.team requests are GET-only. The server cannot post comments, change tasks, track time or upload files. It can update local history and participant roles. Access is limited by the configured Moo.team account's permissions. It uses observed application API endpoints, which may change without notice.
Attachment bytes and rendered pages stay in memory; there is no attachment cache or document temporary directory. Images have a 5 MiB output limit. Selected PDF pages can be returned as images for the assistant to inspect scans and diagrams; there is no automatic OCR transcript. Office extraction reads text and reports visual/layout limitations. Legacy DOC/XLS/PPT, audio, video and non-ZIP archives are unsupported. External links are retained without fetching them.
History defaults to at most 1 MiB compressed per workspace, 200 tasks and 90 days since last observation, with at most 20 change events per task. It stores hashes, IDs, statuses and timestamps, never task/comment bodies or file contents. Expiry and eviction run on the next tracked read. See configuration for storage details, disabling history and limits.
Documentation
Page | Contents |
Credentials, clients, limits and troubleshooting | |
Inputs, output semantics, pagination and endpoint mapping | |
Architecture, tests and release procedure |
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Secure AI access to OpenOak tasks, notes, and Kanban boards.
Read-only AI access to HAVN properties, leads, tasks, files, media, and analytics.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to read structured project context and propose task changes that require explicit human approval, with scoped permissions, idempotency, and a full audit trail.MIT
- AlicenseNot gradedqualityCmaintenanceProvides safe, read-only CRM access for AI assistants with per-key scopes, field masking, rate limits, and a full audit log of allowed and blocked actions.MIT

Xenmark MCP serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to read drawing-review data—projects, drawings, revisions, comments, replies, and notification inbox—through a read-only, locally run connection.938 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read and edit projects, tasks, client requests, comments, and settings over the Model Context Protocol, deployed with the app and authenticated via read-only or read-write bearer tokens scoped to the creating user.MIT