Skip to content

Montage for Kiro IDE

Kiro IDE exposes MCP through workspace and user configuration, with remote OAuth behavior that differs from Kiro Web and Mobile.

Integrations

How do I verify Montage workspace access with Kiro IDE?

Kiro IDE exposes MCP through workspace and user configuration, with remote OAuth behavior that differs from Kiro Web and Mobile. This guide concerns the installed IDE, where a Montage connection can remain personal or follow one repository. Its useful starting point is configuration precedence: a correct account cannot repair a workspace override that sends requests to a different server.

01 / CONFIGUREOne remote endpointUse this client's documented HTTP setup
02 / AUTHORIZEYour workspace accessUse a supported sign-in or credential flow
03 / VERIFYRun signals_statusCheck a real workspace response
Kiro IDE · read-only verification prompt
Using Kiro IDE, 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.
01 / Integrations

Open the IDE configuration deliberately

Use the command palette to choose Kiro: Open workspace MCP config (JSON) or Kiro: Open user MCP config (JSON). On macOS the palette uses Cmd+Shift+P; on Windows and Linux use Ctrl+Shift+P. Inspect existing entries rather than replacing the file. Workspace .kiro/settings/mcp.json takes precedence over the corresponding user-level entry when both define the same server name.

02 / Integrations

Use the remote server shape

Under mcpServers, give montage a url of https://app.montages.co/mcp and leave unrelated entries unchanged. Remote configuration takes a URL, unlike a local server's command and args. Avoid copying an example's autoApprove wildcard. Saving configuration reconnects servers, so finish reviewing the entire entry before saving; a reconnect is still not proof that workspace execution has been authorized.

03 / Integrations

Use IDE-supported OAuth

Current Kiro documentation supports browser OAuth for self-configured remote servers in the IDE and CLI. Review the Montage identity during consent. The IDE supports public OAuth clients, not confidential clients requiring a client secret. Do not add another provider's clientId or callback example to force discovery, and do not assume Web or Mobile honors these same oauth settings.

04 / Integrations

Review loaded tools and approvals

Check the MCP servers tab in the Kiro panel after saving and inspect the tools exposed by the Montage entry. Keep write approvals interactive and exclude tools you do not intend to use. Tool discovery can succeed independently of workspace permission; a familiar tool name in the panel is not evidence that its execution is available to your signed-in account.

05 / Integrations

Confirm the workspace before coding research

Send an explicit request for Montage signals_status only, then compare the returned workspace with the one intended for this repository. Treat an authorization failure as a blocked connection. For missing tools, check the effective workspace override and whether MCP support is enabled in Settings. Stop after the read-only result; neither a Kiro spec nor a coding instruction grants automatic social actions.

Keep the boundaries clear.

  • Self-configured remote OAuth is documented for IDE and CLI; Web and Mobile do not use the same oauth settings.
  • 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.

Know what social media shows about you.
Start with a question.

Get started
montage