Skip to main content

​
Prerequisites

Kiro IDE

Download and install Kiro

Civic Account

Create a free account and configure your tools at app.civic.com

​
Setup

Kiro supports remote MCP servers natively via Streamable HTTP — no local bridge required.
1

Get your Civic credentials

Go to app.civic.com and navigate to Install → MCP URL to get your CIVIC_URL and CIVIC_TOKEN.
2

Open MCP config

Open the command palette and run Kiro: Open workspace MCP config (JSON) to create or edit .kiro/settings/mcp.json.For a global config that applies to all projects, use Kiro: Open user MCP config (JSON) instead (stored at ~/.kiro/settings/mcp.json).
3

Add Civic as an MCP server

{
  "mcpServers": {
    "civic": {
      "url": "${CIVIC_URL}",
      "headers": {
        "Authorization": "Bearer ${CIVIC_TOKEN}"
      }
    }
  }
}
Set the CIVIC_URL and CIVIC_TOKEN environment variables in your shell profile, or replace the ${...} placeholders with your actual values.
4

Enable MCP support

Open Settings (Cmd + , on Mac, Ctrl + , on Windows/Linux), search for MCP, and make sure the setting is enabled.
5

Verify connection

Open the Kiro panel and check the MCP Servers tab — Civic should appear with a connected status indicator.

​
Test Your Connection

Open Kiro’s agentic chat and try: 
"What MCP tools do I have available?"
"List my Google Calendar events for today"
"Check my Gmail inbox"

​
Reference Implementation

For a complete working example, see the Kiro + Civic reference implementation — a Node.js app demonstrating Google Calendar and Gmail integration via Civic Hub, with Kiro steering files and specs included.

​
Troubleshooting

Verify that .kiro/settings/mcp.json is valid JSON and MCP support is enabled in Settings. Check MCP logs via the Kiro panel → Output tab → Kiro - MCP Logs.
Your Civic token may be expired (30-day expiry). Regenerate at app.civic.com under Install → MCP URL. Make sure CIVIC_URL includes ?profile=your-toolkit-name.
Visit app.civic.com to confirm your toolkit has MCP servers configured. An empty toolkit will result in no tools being available.
Kiro uses ${VAR} syntax for env var expansion. Make sure the variables are set in your shell profile and Kiro was launched from that shell, or replace the placeholders with actual values.

​
Need Help?

Troubleshooting

Common connection issues and solutions

Get Help

Ask in our developer Slack