Kiro

Prerequisite

Use Kiro with its MCP settings support or Kiro Power. Kiro connects as an OAuth client requesting memory:read and knowledge:read scopes.

• Endpoint: https://xmemo.dev/mcp.
• Auth mode: OAuth client with memory:read and knowledge:read scopes.
• Config file: ~/.kiro/settings/mcp.json.
• Kiro Power repository: yonro/xmemo-kiro-power @ 2fcccbce60 (plugin.json) provides hosted MCP and Knowledge authoring adapter.
• Readiness status: Evidence required (planned marketplace, not certified). A GitHub custom-Power path is not official-catalog approval.

Install / setup

Add the XMemo server block to ~/.kiro/settings/mcp.json under mcpServers, or install automatically using the XMemo client command. Alternatively, install the custom Kiro Power from yonro/xmemo-kiro-power @ 2fcccbce60.

• OAuth client: configure in ~/.kiro/settings/mcp.json.
• Supports OAuth with memory:read and knowledge:read scopes.
• Run npx @xmemo/client mcp add kiro to install automatically.
• Kiro Power installation: clone or install yonro/xmemo-kiro-power @ 2fcccbce60 (plugin.json) with hosted MCP and explicit Knowledge REST authoring adapter.

npx @xmemo/client mcp add kiro

Set the credential

OAuth path: no static key in settings. Complete browser OAuth consent when Kiro requests access for the memory:read and knowledge:read scopes.

Generate / confirm XMEMO_AGENT_INSTANCE_ID

Generate a stable non-secret instance identifier per local Kiro install so attribution stays consistent across sessions.

export XMEMO_AGENT_INSTANCE_ID='<stable-local-kiro-instance-id>'
# Persist and reuse this value for the same local install

Preserve the existing config block

Use the existing Kiro configuration block rendered on this page. It preserves the OAuth scopes and matches the authoritative config installed by @xmemo/client.

{
  "mcpServers": {
    "XMemo": {
      "url": "https://xmemo.dev/mcp",
      "headers": {
        "X-Memory-OS-Agent-ID": "kiro",
        "X-Memory-OS-Agent-Instance-ID": "${XMEMO_AGENT_INSTANCE_ID}"
      },
      "oauth": {
        "oauthScopes": [
          "memory:read",
          "knowledge:read"
        ]
      }
    }
  }
}

Restart the client

Restart Kiro after updating ~/.kiro/settings/mcp.json or installing Kiro Power so it initiates the OAuth handshake on first request.

Test with a real recall call

Make the first MCP call read-only. This is an actual recall invocation, not a health-check placeholder, and it does not write memory.

recall({ query: "connection check", limit: 1 })

Expected response (literal shape)

A successful call returns the public ranked text shape below; the reference and content are real values from the authorized memory space.

### XMemo Memory Results:
1. Reference: <opaque-memory-id> | Location: <location>
   > <memory content>

Common Errors

Kiro connects through OAuth; common errors relate to authorization grant or scope approval.

• invalid_grant — the OAuth authorization code is invalid, expired, or already used: reconnect Kiro and re-authorize.
• 403 insufficient_scope — approved scopes do not include memory:read: ensure memory:read and knowledge:read are approved.
• Invalid XMEMO_AGENT_INSTANCE_ID values are normalized to no instance attribution rather than raising an auth error.

Certification and readiness

Certification status: Evidence required. Marketplace status: Planned. Integration evidence is required before full certification is granted.

• Certification status: Evidence required.
• Marketplace status: Planned.
• Readiness note: See /product/docs#client-capability-matrix; this matches the authoritative config installed by @xmemo/client.
• Kiro Power status: yonro/xmemo-kiro-power @ 2fcccbce60 custom-Power path does not constitute official Kiro catalog approval.