Integrations
Kiro
Setup detects Kiro and writes both an MCP entry (~/.kiro/settings/mcp.json) and a steering rule (~/.kiro/steering/sigil.md).
sigil initsigil doctorManual config
Section titled “Manual config”{ "mcpServers": { "sigil": { "command": "/Users/you/.sigil/bin/sigil-mcp", "args": [] } }}Use sigil register --print for the correct path on your machine.
Steering rule
Section titled “Steering rule”Kiro’s steering files are the right home for memory instructions — they’re loaded consistently rather than depending on a system prompt you can’t see.
# Memory (Sigil)
Sigil is a persistent memory shared with every other AI agent on this machine.
- Call `prime` at the start of every session.- Before answering about this project, past decisions, or the user's preferences, call `search`.- When the user shares a preference, decision, or constraint, call `remember` with a short self-contained statement.- Pass `cwd` on `search`, `remember`, and `ingest` so memory attaches to the right project.- To read a stored document in full: `list_documents` then `get_document`.Setup writes a version of this automatically. Edit it to taste — it’s yours.
Available tools
Section titled “Available tools”Kiro gets all thirteen MCP tools. The ones that matter most in a Kiro session:
| Tool | |
|---|---|
prime | Load standing context at session start |
search | Facts by natural-language query |
search_entity | People, projects, services by name |
traverse_graph | Walk relations outward from an entity |
remember | Save atomic facts |
ingest | Store a document whole |
Spec-driven workflows
Section titled “Spec-driven workflows”Kiro’s spec workflow is a good fit for ingest. When a spec is finalized, store it:
sigil ingest ./.kiro/specs/payments-v2/design.mdThe full text is retained and facts are extracted from it — so a later question about the design gets an atomic answer, and get_document gets the source when you need the whole thing.
Troubleshooting
Section titled “Troubleshooting”sigil connect --clients kirosigil doctor --deepRestart Kiro after registering; it reads mcp.json at startup.
If tools are available but never called, strengthen the steering rule — particularly the “before answering” line.