Mastra adds built-in MCP server for agents and workflows
Start here
Mastra released a built-in MCP server that exposes its agents, workflows and tools at /api/mcp once the @mastra/mcp package is installed and an auth provider is configured. It ships call_agent, start_workflow and get_trace tools, and routes each MCP call through the same server routes and RBAC/FGA checks as standard HTTP requests; users can limit what is exposed via toolsets, include and exclude. In production, Mastra says it will not expose the MCP server without an auth provider, though this can be overridden with enabled: true. Requests typically require a bearer token verified by that provider. The feature requires @mastra/core@1.83.0 or later, and Mastra documents connecting it to Claude Code via claude mcp add with a bearer token.
Generated from reports · updated 4 h ago
Report timeline
Follow the reports to see the event from different sides.
- Mastra BlogMastra launches built-in MCP server exposing agents, workflows and tools at /api/mcp
Mastra released a built-in MCP server that exposes its agents, workflows and tools at /api/mcp once the @mastra/mcp package is installed and an auth provider is configured. The server ships call_agent, start_workflow and get_trace tools, routes each MCP call through the same server routes and RBAC/FGA checks as standard HTTP requests, and lets users limit exposure via toolsets, include and exclude. It requires @mastra/core@1.83.0 or later, and Mastra documents connecting it to Claude Code with claude mcp add and a bearer token.
Heat for this event
- Current, comparable range
- 4
- Peak, comparable range
- 4November 18 05:00
- Change in 24 hours
- –
The trend compares the same participants over hours observed continuously, so its range can be narrower than the current heat count. Hover or tap the chart for hourly heat; the arrow keys move through it.