Skip to main content

MCP Servers

Overview

The Mastra Agent Framework exposes its tool registries as Model Context Protocol (MCP) servers. Each MCP server wraps a domain-specific tool registry, making the tools available to any MCP-compatible client (VS Code Copilot, Claude Desktop, custom agents).

MCP servers are instantiated through the active Mastra artifact loaders and then merged into the runtime configuration in apps/runtime/src/mastra-runtime.ts. Each server factory returns a fresh MCPServer instance wired to a source-owned tool registry.

Server Summary

ServerVersionToolsDomainSkip/Opt-in Flag
Admin MCP Server1.0.011Base PlatformMASTRA_SKIP_ADMIN_MCP
K12 Safety MCP Server1.0.028K12 EducationMASTRA_SKIP_K12_MCP
Reasoning Engine MCP Server1.0.08Reasoning EngineMASTRA_INCLUDE_REASONING_ENGINE=true
Docs MCP Server1.0.04Documentation (all)MASTRA_SKIP_DOCS_MCP
K12 Docs MCP Server1.0.04K12 DocsMASTRA_SKIP_DOCS_MCP
SDAC Docs MCP Server1.0.04SDAC DocsMASTRA_SKIP_DOCS_MCP
TAP Docs MCP Server1.0.04TAP DocsMASTRA_SKIP_DOCS_MCP
RE Docs MCP Server1.0.04RE DocsMASTRA_SKIP_DOCS_MCP

Total source-backed tools across the listed runtime MCP servers: 67. The separate token-gated diagnostics MCP server exposes 9 additional tools, so the generated MCP inventory tracks 76 tools total when diagnostics is included.

The skip flags are parsed through the environment schema. Reasoning Engine inclusion is exposed through env.includeReasoningEngine, which reads MASTRA_INCLUDE_REASONING_ENGINE=true directly.

Documentation

MCP server documentation is split into two audiences:

  • Internal -- Architecture, factory patterns, source paths, testing, and implementation details for engineers maintaining the MCP layer
  • External -- Available servers, tool inventories, connection methods, and usage guidance for MCP client developers