How do I connect Montage to Zed Agent rather than an external agent?
Zed Agent can use remote MCP servers configured through AI settings or context_servers. That editor-owned connection is distinct from an external ACP agent's configuration and from native tooling running in a terminal thread. Decide which surface will actually call Montage before editing settings. This documented setup uses Zed's standard remote OAuth prompt without inventing an Authorization header or a product partnership.
{
"context_servers": {
"montage": {
"url": "https://app.montages.co/mcp"
}
}
}Call Montage signals_status in this Zed Agent session. Report the returned workspace and coverage; do not run collection or write tools.Choose the Zed-owned agent surface
Open the Zed Agent workflow that should receive Montage tools. If you are instead using an external ACP agent, inspect that agent's native MCP documentation rather than assuming Zed settings are inherited. The same distinction applies to an assistant launched inside a terminal thread: sharing an editor window does not imply sharing server registration or authorization state.
Add the remote context server
In Settings, use AI MCP Servers and Add Remote, or merge the context_servers.montage.url entry shown below into your Zed settings. Retain existing context servers and keep the complete HTTPS path. This is a remote server address, not a command to execute locally or a request to install a Montage extension.
Let the standard OAuth prompt work
Without an Authorization header, Zed's documented remote flow prompts for standard OAuth. Review the named Montage account and permissions before consent, then return to the editor. Do not preempt this flow by pasting a token into a header merely because another server example uses one. An unrelated model provider credential cannot authorize the Montage workspace.
Review tools in the active conversation
Use Zed's current server and Agent controls to confirm that Montage is available where you intend to work. Keep the first instruction explicitly read-only. If tools appear in a different agent surface, resolve that configuration boundary first rather than duplicating credentials across Zed, an external ACP agent and a terminal-based assistant.
Prove access with signals_status
Ask Zed Agent to call Montage signals_status and inspect the actual workspace result. If authentication fails, revisit the remote server's OAuth prompt and account selection. If tools are missing, verify context_servers scope and whether this is truly Zed Agent; if HTTP initialization fails, check the endpoint and client release. Do not label an external agent connected based solely on Zed's successful response.
Keep the boundaries clear.
- Zed Agent, external ACP agents and terminal threads may own separate MCP configuration.
- The standard OAuth path assumes no manually supplied Authorization header.
- Documented setup does not certify every Zed version or external agent combination.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.