How do I locate LM Studio’s app-managed Montage definition?
LM Studio’s local model files and its app MCP plugin configuration are different surfaces. Locate the app-managed definition before changing unrelated inference settings, and treat the remote URL as registration rather than evidence that the local model can access a Montage workspace. Locate the definition through LM Studio’s app controls before adapting it. Model files and unrelated inference services are not the owner of mcp.json, and a URL accepted by the app is still not account authorization.
Help me locate LM Studio’s app-managed Montage definition. Confirm this task concerns LM Studio’s app plugin workflow rather than another local inference service. Attempt signals_status only if approved compatible auth already exists. No writes.Identify the owning application
Confirm this task concerns LM Studio’s app plugin workflow rather than another local inference service. Sharing model files or a machine does not imply a common MCP configuration. The owning-app note should exclude unrelated inference runtimes, preventing an operator from editing another service’s configuration because both use the same local model.
Locate the MCP file
Use the documented Program, Install and Edit mcp.json controls for the installed app. Inspect existing mcpServers definitions before adding or replacing any Montage entry. The current LM Studio documentation controls the path to mcp.json; a familiar filename elsewhere on disk does not prove the app loads it.
Review the hosted definition
Check mcpServers.montage.url against the remote HTTPS endpoint. A command launching local inference does not register the hosted Montage tool server or authorize its account-scoped operations. The remote registration artifact contains the hosted URL under mcpServers, not an install command for a local Montage service or model adapter.
Qualify account authorization
Inspect supported auth facilities independently of the URL. Remote transport documentation and header examples are not a guarantee that this LM Studio release can complete Montage OAuth. A header example is conditional configuration guidance, not evidence that this account has an approved credential or that standard OAuth is supported.
Report the actual boundary
Attempt signals_status only if approved compatible auth already exists. Otherwise record that the app definition is located but private-workspace execution remains blocked, with a documented OAuth-client fallback. If authorization is unavailable, an OAuth-capable client is the honest fallback; do not present the local model’s explanation of tools as a workspace receipt.
Keep the boundaries clear.
- The remote registration artifact contains the hosted URL under mcpServers, not an install command for a local Montage service or model adapter.
- If authorization is unavailable, an OAuth-capable client is the honest fallback; do not present the local model’s explanation of tools as a workspace receipt.
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.