Agent Tools
Myco exposes MCP tools and slash-command skills that your agents can use without leaving their native workflows. Local tools serve coding agents on your machine, and the Cloud MCP server serves cloud agents from synced Grove knowledge. Both speak Model Context Protocol and discover their tools automatically.
Automatic context injection
Before any tool is called, Myco can route context at three points automatically:
- Session start — a Cortex project briefing gives the agent a pre-computed understanding of the project before it asks a single question
- Per prompt — relevant spores are retrieved via vector search, providing targeted context for the current task
- Pre-Read — Canopy provides per-file anatomy so the agent can decide whether to follow through with a full read
These context routes augment the agent’s native memory and tools. Myco does not replace the agent’s reasoning or workflow. See the Lifecycle docs for more on how this works.
Local MCP tools
Seven local tools are available to any symbiont Myco has connected. When the project is connected to a Myco Collective, four additional collective_* tools are also registered.
The MCP surface is intentionally limited to read and editorial operations — symbionts use Myco’s project intelligence; they do not administer Myco. Administrative operations such as restart, update, backup, restore, and maintenance live in the CLI and UI. See Actors and Boundaries.
Every vault-scoped tool accepts optional grove_id and project_id fields so agents can work with the same Grove/project selection model shown in the dashboard.
Search & Cortex
| Tool | Purpose |
|---|---|
myco_search |
Semantic + keyword search across sessions, spores, plans, skills, and Canopy file summaries. Results include stable IDs and retrieve hints pointing to the owning entity tool. |
myco_cortex |
Cortex project intelligence: digest (op=digest), generated instructions, Canopy map (op=canopy_map), Canopy entries (op=canopy_entry), pending notifications (op=notifications), per-Grove maintenance summary (op=maintenance_summary), and cross-Grove project activity (op=projects_activity). |
Entity tools
| Tool | Purpose |
|---|---|
myco_plans |
List, retrieve, save, or delete plans using `op=list |
myco_sessions |
List or retrieve session history using `op=list |
myco_skills |
List, inspect, or read auto-generated skills with their full lineage. |
myco_spores |
List, retrieve, save, supersede, or consolidate spores using `op=list |
myco_agent |
Read agent run history using `op=runs |
Cloud MCP tools
A separate, read-only tool surface for cloud agents (Anthropic Managed Agents, N8N, OpenAI Workflows, etc.). Six tools follow the same search-then-entity access pattern as local MCP while limiting operations to synced team reads. See the Cloud MCP docs for the full reference and setup.
Slash-command skills
Myco ships two slash command skills that provide guided workflows. Type the command in your agent’s prompt to activate. Beyond these, Myco auto-generates project-specific skills from your vault knowledge — see the Skills docs for the full curation lifecycle.
| Command | Purpose |
|---|---|
/myco |
The primary skill for ongoing work. Use when making design decisions, debugging non-obvious issues, encountering gotchas, or needing context about prior work. Provides guidance on when and how to use each MCP tool. |
/myco-rules |
Keep AGENTS.md minimal, durable, and canonical across agents. |