When is LM Studio's remote MCP setup sufficient for Montage?
LM Studio documents remote MCP URLs in its app's plugin configuration. That establishes a remote transport option, not certified OAuth or login parity with Montage. Its documentation includes authorization-header examples, which must not be mistaken for automatic user sign-in. Use this conditional setup only when your installed version and approved account authorization can support it; otherwise a proven OAuth client is the appropriate fallback.
{
"mcpServers": {
"montage": {
"url": "https://app.montages.co/mcp"
}
}
}If approved authorization is available, call Montage signals_status only. Otherwise stop and report that login is unsupported; do not invent a successful response.Inspect the app's MCP configuration
Open the Program tab and follow Install, then Edit mcp.json, using the current app documentation to locate the controls. Review existing mcpServers entries and preserve unrelated plugins. This is LM Studio's app-managed MCP setup, not the configuration of a different local inference service that happens to use the same model files.
Register the hosted remote address
Merge the Cursor-style mcpServers.montage URL entry shown below into mcp.json. The remote address is documented configuration, but the snippet intentionally contains no Authorization header. Saving it allows the app to attempt transport initialization; it does not prove a successful account login or give a locally running model access to a private Montage workspace.
Resolve the authentication limitation first
Remote transport is documented, but OAuth/login parity is not certified here. If your installed release cannot complete Montage authorization, an existing approved Team credential may be supplied securely by its owner using supported controls. Do not create keys for this guide or paste credentials into examples. Free or Pro users needing unsupported authentication should choose a proven OAuth client instead.
Review permissions independently of model hosting
Running inference locally does not remove the remote service's authorization requirements, workspace limits or data handling considerations. Inspect which MCP tools the app exposes and keep collection and write operations disabled for setup. A model's ability to describe an advertised tool is not evidence that an authorized server call actually executed.
Require a real signals_status response
Only after supported authorization is configured, request Montage signals_status and inspect the actual workspace result. If it fails with an auth error, stop and use the approved credential-owner path or OAuth-client fallback; do not infer success from remote URL acceptance. For transport errors, recheck mcp.json and the endpoint. No collection job or paid inference is needed as a substitute connection test.
Keep the boundaries clear.
- Remote MCP transport is documented; Montage OAuth/login parity in LM Studio is not certified.
- Existing approved Team credentials can be supplied securely only by their owner; this guide creates none.
- Free/Pro users blocked by unsupported auth should use a proven OAuth client instead.
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.