Kiro Setup

Overview

Kiro is AWS's agentic IDE — a spec-driven development environment with MCP support built in. MCP isn't gated by plan: the free tier connects to Tempreon exactly 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 free tier includes open-weight models (Qwen3 Coder, DeepSeek, MiniMax) alongside Claude 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 (or the Kiro panel's MCP servers tab) → browser opens for OAuth → approve → done.

One-click install: with Kiro installed, Add to Kiro writes the config for you — then approve the browser OAuth prompt and you're done.

Prerequisites

• Kiro installed (macOS, Windows, or Linux) — any plan, including free
• 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

If the same server appears in both, the workspace config wins. For Tempreon, user scope is usually what you want — your context is yours, not per-project.

Prefer clicking over editing files? The Kiro panel has an MCP servers tab where you can add the server directly.

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

When Kiro connects, it runs the OAuth flow automatically via dynamic client registration: a browser tab opens with the Tempreon consent screen. Sign in if prompted, review the request, and approve. Kiro stores the token and reconnects on its own from then on.

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 reuses the IDE's MCP configs. 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 appears in both the workspace and user files, the workspace copy wins — make sure the one Kiro is actually reading has the correct URL.

Browser doesn't open for authorization. Check pop-up blockers and that a default browser is set at the OS level, then retry the connection from the MCP servers tab.

Tools not appearing in chat. Restart Kiro (or reload the window) after adding the config — the tool list refreshes at session start.

On the free tier and wondering if that's the problem. It isn't — MCP isn't plan-gated in Kiro. If the connection fails, it's one of the items above, not your plan.

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