Metainformant Src Metainformant Mcp

---
name: metainformant-src-metainformant-mcp
description: METAINFORMANT rules for directory src/metainformant/mcp. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
---

# METAINFORMANT — `src/metainformant/mcp`

Before editing files in this subtree:

- Read [`AGENTS.md`](../../../src/metainformant/mcp/AGENTS.md) for this folder (canonical technical context).
- Optional overview: [`README.md`](../../../src/metainformant/mcp/README.md).
- Global rules: [`CLAUDE.md`](../../../CLAUDE.md) at repo root (uv, `output/`, `.tmp/`, real implementations).
- Testing policy: [`docs/REAL_IMPLEMENTATION_POLICY.md`](../../../docs/REAL_IMPLEMENTATION_POLICY.md).
- Use `metainformant.core.io` for file I/O and `metainformant.core.utils.logging` for logs.

## Module surface (generated, validated)
- Purpose: MCP (Model Context Protocol) package for METAINFORMANT.

Provides a stdio JSON-RPC 2.0 MCP server (:mod:`metainformant.mcp.server`) and
a declarative tool registry (:mod:`metainformant.mcp.registry`).  Tools are
bundled tool adapters under ``metainformant.mcp.tools`` plus this package's
``tool_adapters`` module; every tool is registered through
``metainformant.mcp.registry.ToolRegistry``.
- Public submodules: `registry`, `server`, `tool_adapters`, `tools`.
- Canonical import: `import metainformant.mcp` (submodules: `from metainformant import mcp` then `mcp.<submodule>`).
- Test entry point: `uv run pytest tests/mcp -q` (one pytest directory per invocation).

Keep changes scoped; match existing patterns in this directory.