One connection. A real first result.
Add the server, sign in and approve, then verify your workspace connection. No key to copy for an OAuth-capable agent.
Montage for CrewAI
CrewAI supports MCP through an agent's mcps field and through the lower-level MCPServerAdapter in crewai-tools.
Read guideMontage for Microsoft Foundry Agents
Microsoft Foundry Agent Service consumes remote MCP endpoints through a managed agent runtime.
Read guideMontage for Microsoft AutoGen
AutoGen's autogen_ext.tools.mcp module supplies remote server parameters, tool adapters, and an MCP workbench.
Read guideMontage for Spring AI
Spring AI's MCP Client Boot starters configure named connections and manage their lifecycle with the application context.
Read guideMontage for Vercel AI SDK
Vercel AI SDK creates a lightweight MCP client and converts discovered tools into the application's tool interface.
Read guideMontage for OpenAI Responses API
OpenAI Responses can use a hosted MCP tool directly, with server_url and server_label describing the remote service.
Read guideMontage for Google ADK
Google ADK uses McpToolset to adapt remote server tools into agent tools.
Read guideMontage for Google GenAI SDK
The Google GenAI Python SDK documents experimental MCP support by accepting an initialized MCP session as a tool.
Read guideMontage for Anthropic MCP connector
Anthropic's MCP connector lets the Messages API reach remote MCP servers without a separate application-side MCP client.
Read guideMontage for Kiro CLI
Kiro CLI loads MCP servers through configuration files and agent-specific definitions, with a documented precedence hierarchy.
Read guideMontage for Mastra
Mastra separates MCPClient, which consumes remote tools, from MCPServer, which exposes agents and workflows to other systems.
Read guideMontage for Docker Agent
Docker Agent can connect directly to remote MCP servers through YAML toolsets.
Read guideReview Claude Code repository reach before sharing Montage
An existing coding session may reach Montage successfully while a teammate cannot see the server at all.
Read guideRecover expired Montage consent in Claude Code
A previously working Claude Code session can lose Montage authorization without any change to the server URL.
Read guideMove a Claude Code Montage workflow to another working copy
Opening another checkout is a configuration transition, not a reason to assume that server registration or account access followed the files.
Read guideHold Claude Code at a read-only Montage checkpoint
Coding assistants can move from investigation into implementation within one conversation.
Read guideQualify Claude Desktop connector policy without changing it
A missing remote connector option can be an organizational restriction rather than a Montage outage.
Read guideRepair a Claude Desktop connector authorized to the wrong account
A connector can exist and still point at an unintended Montage workspace because the consent browser was signed in differently than expected.
Read guideCarry a Claude Desktop connector into the intended conversation
Successful consent does not guarantee that every Claude conversation can use the same connector.
Read guideReview Claude Desktop Montage actions before approving research
A remote connector expands what Claude can propose, but proposal and execution remain different events.
Read guideCompare Cursor project and personal Montage registration
A Cursor project can contain an MCP definition while the editor also has personal server settings.
Read guideRecover a rejected Montage OAuth flow in Cursor
Cursor may recognize a remote server yet fail when a workspace tool needs authorization.
Read guidePreserve Cursor MCP settings when moving a project
Moving a repository should not replace unrelated MCP servers or export account authorization.
Read guideCreate a Cursor checkpoint before Montage workspace writes
A Cursor agent may be authorized to edit code while a Montage task should remain observational.
Read guide