How do I verify Montage workspace access with GitHub Copilot CLI?
GitHub Copilot CLI has an interactive MCP dashboard and an add-server form, distinct from editor configuration. Organization registry and allowlist policy can restrict which custom servers may run. Montage is a custom remote server in this workflow, not the CLI's built-in GitHub server or a claim that GitHub has verified a Montage connector. Begin with the terminal environment that will own authorization.
Using GitHub Copilot CLI, call only Montage signals_status as the first live operation. Report the actual workspace identity and coverage from the tool response. If authentication, transport, or the tool is unavailable, stop and explain the blocker. Do not start collection, recurring tracking, writes, publishing, messaging, or social actions.Check the CLI’s policy context
Open /mcp in an interactive Copilot CLI session and inspect configured servers before adding Montage. If an organization supplies your subscription, check whether registry and allowlist policies permit this endpoint. Do not evade a managed restriction with a second server name. The built-in GitHub MCP server is unrelated to Montage and does not establish access to external workspaces on your behalf.
Use the interactive HTTP form
Enter /mcp add, supply a unique server name, and choose HTTP rather than STDIO or legacy SSE. The official form identifies HTTP as Streamable HTTP. Set the URL to https://app.montages.co/mcp, leaving local command fields unused. This avoids guessing flags for the separate copilot mcp add subcommand, whose syntax should be checked against the installed release before scripting it.
Limit the form’s tool selection
The form includes a Tools field whose default wildcard exposes everything. Prefer the actual status tool name for initial verification instead of inheriting that broad default. Tool filtering limits what the model can request, but it does not replace server authorization. Keep any existing approval policy intact and do not make the terminal globally permissive just to simplify a connection diagnostic.
Authorize the custom server appropriately
Use the CLI's supported authentication controls for the remote server and review the Montage identity during consent. Do not confuse the Connectors dashboard with a guarantee that every custom server shares connector-managed authentication. If your installed version cannot complete the required flow, stop with that limitation. Any manually configured credential must already be approved and must remain outside prompts and repository configuration.
Inspect an actual status call
Ask Copilot CLI for Montage signals_status only and examine the real server result, not a generated description of available tools. Verify the workspace before continuing terminal research. On policy denial, return to the administrator rather than bypassing controls; on authentication denial, repair the grant. No collection, file modification, publishing, or social action is part of this initial check or authorized by its success.
Keep the boundaries clear.
- Managed registry and allowlist policies apply to custom CLI MCP servers; no verified Montage connector is claimed.
- Documented setup, not live interoperability certification. A visible tool catalog is not workspace authorization.
- First live operation: read-only signals_status. No automatic collection, recurring tracking, or social actions; broader actions need separate explicit authorization.
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-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.