alayasiki-mcp

# MCP agent interface `alayasiki-mcp` exposes the standard runtime through MCP protocol `2024-11-05`. Local clients use newline-delimited JSON-RPC on stdio; the authenticated HTTP API also hosts the legacy SSE transport. This implementation does not claim support for the newer Streamable HTTP transport. ## Local stdio ```sh cargo run -p alayasiki-mcp -- --data-dir /path/to/agent-db ``` The default database directory is `$HOME/.alayasiki-mcp` (`USERPROFILE` on Windows). `ALAYASIKI_DATA_DIR` or `--data-dir` overrides it. Help/version commands exit before opening a database. Only protocol messages go to stdout. EOF closes the connection, joins the worker at a job boundary and flushes the repository. The local process is trusted through OS permissions: its principal has the `admin` role, with tenant `local` and subject `local-agent`. `ALAYASIKI_MCP_TENANT` and `ALAYASIKI_MCP_SUBJECT` select a different local identity. Never open a data directory concurrently in another process; use remote SSE to share one server-owned database. Local MCP and HTTP have different default directories. Initialization requires `protocolVersion`, `capabilities`, and `clientInfo`: ```json {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"example","version":"1"}}} {"jsonrpc":"2.0","method":"notifications/initialized"} {"jsonrpc":"2.0","id":2,"method":"tools/list"} ``` Notifications receive no response. Ping, discovery, resource reads and prompts use standard JSON-RPC request/result/error envelopes. Tool results contain a text block with a JSON value; execution failures return `isError: true` with sanitized messages. ## Tools | Name | Arguments | Behavior | |---|---|---| | `alayasiki_query` | Full query DSL, including `query`, modes, filters and snapshot | Authorized GraphRAG with evidence/citations | | `alayasiki_ingest` | `content`, optional metadata/idempotency key, or canonical `request` | Authorized auto…