MCP Tools

The server registered through MCP Integration provides these read-only tools and resources to your agent. You do not invoke them directly; the agent selects one for the intent of your request.

Choose by intent

Request intent	Tool to use
Exact count, filters, or full inventory	The matching `agentteams_*_list`. Each call returns one page, so use `meta.total` for the count and request every page from `page=1` through `meta.totalPages` for the full inventory.
Topic or relevance discovery	`agentteams_search`. Check `meta.truncatedByTokenBudget`, and do not treat search results as an exact count or complete inventory.
Known ID or the full selected item	The matching `agentteams_*_get`. Prefixed IDs from list/search results or web links are normalized automatically.
Create, update, delete, download, files	The `agentteams` CLI. Also use the CLI when MCP is disconnected or the required read tool is unavailable. CLI commands do not call the MCP server as an internal transport.

List results are metadata inventories and do not chain full-content requests. Fetch details only for the items you need.

Every search/list/get tool reads only the single project bound to the current MCP server or context client. Passing an ID from another project cannot change that scope.

Search tool

Tool	Role
`agentteams_search`	Unified entity search across the project (semantic + keyword)

The eight supported internal entity types are plans, completion reports, co-actions, post-mortems, conventions, documents, code reviews, and comments.

Exact list tools

Every list tool returns the paginated data/meta response verbatim within the caller’s project permissions and visibility scope.

Tool	Optional filters
`agentteams_plan_list`	`title`, `search`, `status`, `type`, `priority`, `assignedTo`, `createdByMemberId`, `dateFrom`, `dateTo`, `page`, `pageSize`
`agentteams_report_list`	`search`, `planId`, `status`, `reviewStatus`, `createdByMemberId`, `dateFrom`, `dateTo`, `page`, `pageSize`
`agentteams_coaction_list`	`search`, `status`, `visibility`, `source`, `createdByMemberId`, `dateFrom`, `dateTo`, `page`, `pageSize`
`agentteams_postmortem_list`	`search`, `planId`, `status`, `createdByMemberId`, `dateFrom`, `dateTo`, `page`, `pageSize`
`agentteams_document_list`	`q`, `createdByMemberId`, `tags`, `tagPrefix`, `untagged`, `favorite`, `visibility`, `archived`, `page`, `pageSize`
`agentteams_convention_list`	`category`, `scope`, `archived`, `search`, `createdByMemberId`, `page`, `pageSize`
`agentteams_codereview_list`	`search`, `status`, `targetType`, `dateFrom`, `dateTo`, `severity`, `sourcePlanId`, `sourceCompletionReportId`, `createdByMemberId`, `page`, `pageSize`
`agentteams_comment_list`	Plan: `planId`, `type`, `order`; finding: `findingId`, `order`; task: `taskId`, optional `planId`, `order`; document: `documentId`, `order`; shared `page`, `pageSize`

agentteams_comment_list requires exactly one known plan, code-review finding, plan-task, or document parent. There is no project-wide comment list.

Each listed comment carries replyCount, so replies are visible as a signal. Read reply bodies with the CLI: agentteams comment reply-list --id {commentId}.

The maximum pageSize is 100. Dates use YYYY-MM-DD; document untagged and favorite are booleans; tags is a non-empty string array.

Detail tools

Tool	Role
`agentteams_plan_get`	Full plan (body + structured tasks + progress)
`agentteams_report_get`	Full completion report
`agentteams_coaction_get`	Full co-action
`agentteams_postmortem_get`	Full post-mortem
`agentteams_document_get`	Full document (body included)
`agentteams_convention_get`	Full convention
`agentteams_codereview_get`	Full code review and findings
`agentteams_comment_get`	Full comment
`agentteams_codereview_finding_get`	One finding plus its parent review header

Use the existing public name agentteams_codereview_get; agentteams_code_review_get is not exposed. Comment IDs are raw and have no canonical prefix. See Entity Types & IDs for the other prefix rules.

Resource templates

Resource URI	Content
`agentteams://plan/{id}`	Full plan (JSON)
`agentteams://document/{id}`	Full document (JSON)
`agentteams://convention/{id}`	Full convention (JSON)

A resource returns exactly the same data as the detail tool for the same ID.

Usage examples

Exact count of open co-actions

Call agentteams_coaction_list with status=OPEN and page=1.
Use meta.total as the count.
If you need every item, request page=1..meta.totalPages.

Search the topic with agentteams_search.
Check meta.truncatedByTokenBudget.
Fetch only the needed results with the matching detail tools.

Fetch a known ID

Skip search and pass the ID directly to the matching agentteams_*_get.

Target config file per scope

The files agentteams mcp install works with, per client.

Client	User scope	Project scope
Claude Code	`~/.claude.json`	delegates to `claude mcp add`
GitHub Copilot CLI	`$COPILOT_HOME/mcp-config.json`	`.mcp.json`
OpenCode	`opencode.jsonc`	`opencode.json`
Amp	`settings.json`	delegates to `amp mcp add`
Cursor CLI	`~/.cursor/mcp.json`	`.cursor/mcp.json`
Kimi CLI	`~/.kimi-code/mcp.json`	`.kimi-code/mcp.json`
Antigravity	`~/.gemini/config/mcp_config.json`	`.agents/mcp_config.json`
Codex	`config.toml` (fragment, manual)	`config.toml` (manual)

Codex and Copilot user config roots honor CODEX_HOME and COPILOT_HOME, respectively.
When the CLI writes a file itself, it preserves existing entries and comments. If the file cannot be parsed, nothing is written and the run is reported as failed.