Custom MCP Connectors
Planned / Not Yet Implemented
Section titled “Planned / Not Yet Implemented”Custom MCP Connectors are planned for admin-provisioned MCP-compatible server URLs. They are separate from the current built-in first-party provider connectors.
Intended Shape
Section titled “Intended Shape”- Admin-only connector creation with explicit trust acknowledgement.
- Server-side probing for MCP capabilities and authentication methods.
- Support for no-auth, bearer/basic, and OAuth/DCR-style setup only when policy allows it.
- Per-function permission preferences such as ask, allow, and deny.
- Qualification before exposing an MCP connector to chat/search flows.
- Strong audit logging, server-side authorization, TLS/domain policy, and safe credential storage.
Current State
Section titled “Current State”- The extension spec and story exist as deferred planning material.
- No current built-in connector runtime uses literal MCP server integration.
- Current built-in live connectors use first-party provider APIs and domain-oriented Mastra tools.
Canonical Sources
Section titled “Canonical Sources”docs/features/connectors/spec-mcp-extensions.mddocs/features/connectors/stories/custom-mcp-connector.stories.mddocs/features/connectors/tests/custom-mcp-connector.featuredocs/features/connectors/spec.md