# IDEA-013: iEvo MCP Server for Self-Documentation

**Date:** 2026-03-04
**Source:** user
**Status:** raw

## Idea

Build an MCP server for iEvo itself — similar to how OpenAI ships an MCP server for their own developer docs. Agents working inside iEvo projects would be able to query live iEvo documentation, pipeline conventions, and agent specs via MCP.

Inspired by the pattern:
```toml
[mcp_servers.openaiDeveloperDocs]
url = "https://developers.openai.com/mcp"
```

The iEvo equivalent would expose: pipeline conventions (IEVO.md), agent catalog, REQ/PLAN/ACC formats, and CLI reference — queryable by any agent via MCP tool calls.

Also interesting: agent config fields like `model_reasoning_effort` and `sandbox_mode = "read-only"` as first-class agent config options.

## Why

Agents could confirm iEvo-specific APIs, conventions, and pipeline rules in real time instead of relying on static context injection. Reduces hallucination about iEvo internals and enables self-documenting tooling.
