Kiro Setup

Overview

Kiro is AWS's agentic IDE — a spec-driven development environment with MCP support built in. Nothing in Kiro's plans or pricing gates MCP: the tiers differ on credits and model access, so the free tier connects to Tempreon the same way the paid tiers do. Connecting means your AI in Kiro loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns — the same intelligence layer you use across every other tool.

Kiro's model lineup spans open-weight models (Qwen3 Coder Next, DeepSeek 3.2, MiniMax M2.1) alongside Claude and GPT models. All of them get your Tempreon context through this one Bridge, because MCP lives in the harness, not the model — switch models freely and your context comes along.

Quick path: add the Tempreon URL to .kiro/settings/mcp.json → click the authenticate popup → approve in the browser → done.

One-click install: with Kiro installed, Add to Kiro prepares the config for you — Kiro shows a confirmation dialog before anything is written, then you approve the browser prompt and you're done.

Prerequisites

• Kiro IDE or Kiro CLI on macOS, Windows, or Linux — any plan, including free. Remote MCP servers aren't supported in Kiro Web or Kiro Mobile
• On a managed install, MCP not disabled by your administrator (Kiro reports this directly as "MCP has been disabled by your administrator")
• A Tempreon account with at least one available Bridge slot
• A working default browser for the authorization step

Step-by-Step Setup

1. Choose where to configure it

Kiro reads MCP servers from two files:

• Workspace: .kiro/settings/mcp.json — applies to the current project only
• User: ~/.kiro/settings/mcp.json — applies everywhere

The files merge, but on a name collision the higher scope replaces the lower entry whole. The order, highest first, is agent config (a custom agent's own mcpServers field) → workspace → user. For Tempreon, user scope is usually what you want — your context is yours, not per-project.

The Kiro panel's MCP Servers tab is where you confirm and manage connections. Adding from there (the + button, or the Open MCP Config icon) opens the same mcp.json for editing, so it isn't a form-based alternative — for a genuine no-editing path, use the Add to Kiro link above.

2. Add the Tempreon entry

{
  "mcpServers": {
    "tempreon": {
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"
    }
  }
}

The URL is the entire configuration — no tokens, headers, or client IDs. It's also shown in your Bridges dashboard.

3. Authorize in the browser

After you save, a popup appears in the lower-right corner asking you to authenticate the server. Click authenticate and allow Kiro to open the external website — a browser tab opens with the Tempreon consent screen. Sign in if prompted, review the request, and approve. Kiro handles the OAuth handshake itself via dynamic client registration, and refreshes the token transparently during a session.

4. Verify the connection

In a Kiro chat, ask:

"What Tempreon tools do you have access to?"

If Kiro lists Tempreon's tools, the Bridge is live.

Bonus: the Kiro CLI carries over the IDE's MCP configuration. Connect once in the IDE and Tempreon is available in your terminal sessions too.

Troubleshooting

Connection fails immediately. Check the URL ends in /mcp — no trailing slash. The full URL is https://api.tempreon.com/functions/v1/tempreon-mcp/mcp.

Server configured but not connecting. If Tempreon is defined more than once, the highest scope wins outright — an agent config beats the workspace file, which beats the user file. Make sure the entry Kiro is actually reading has the correct URL.

Browser doesn't open for authorization. Look for the authenticate popup in the lower-right corner first — that click is what opens the browser. If you dismissed it, re-save the config to trigger it again, then check pop-up blockers and that a default browser is set at the OS level.

Tools not appearing in chat. Kiro hot-reloads on save, so a restart is not the fix. The reload lands at the next idle boundary, between turns, so a change saved mid-turn waits for the current turn to end. After that, check that MCP support is enabled in Settings, that the JSON parses, and that Tempreon isn't also defined at a higher scope.

"MCP has been disabled by your administrator." Enterprise policy rather than a config problem — your admin has turned MCP off or limited it to an allowed list, so ask whether Tempreon can be added to it.

On the free tier and wondering if that's the problem. It isn't — Kiro's tiers differ on credits and models, not MCP. If you're in Kiro Web or Kiro Mobile, though, remote MCP servers aren't supported there; use the IDE or CLI.

Also connect: OpenCode · Claude Code · Cursor

Try saying...

• "Start my session." — triggers session_start to load your Core Imprint
• "Remember: we chose DynamoDB single-table design for the orders service." — stores an architecture decision your AI will surface in future sessions
• "What do we know about this project's deployment setup?" — searches your Knowledge Vault