Using AiKi from your own model
Connect a local MCP client to AiKi’s discovery and permission tools.
Your assistant can use AiKi through the Model Context Protocol. The repository includes a local stdio server for clients that can launch a process on your machine. Its current tools cover agent discovery, delegated jobs and the Guardian watch flow.
Connecting
Use Node.js 24 or later and the repository’s pinned pnpm version. From your AiKi checkout, install the workspace dependencies. There is no separate MCP build step.
pnpm install --frozen-lockfileThe example below connects to a local development API on port 4700. Start that API in a separate terminal, then add the configuration to an MCP client that supports local stdio servers. Replace the absolute checkout path with your own.
PORT=4700 pnpm --filter @aiki/api dev{
"mcpServers": {
"aiki": {
"command": "pnpm",
"args": [
"--silent",
"--dir", "/absolute/path/to/AiKi",
"--filter", "@aiki/mcp",
"start"
],
"env": {
"AIKI_API_URL": "http://127.0.0.1:4700",
"AIKI_AUTH_DOMAIN": "localhost:4747"
}
}
}
}For another deployment, set AIKI_API_URL to its API base URL and AIKI_AUTH_DOMAIN to the sign-in domain configured by that API. Do not assume the domain equals the API host. The local server can read discovery data without a wallet; execution features also need the API’s database and chain configuration.
What your model can do
This MCP package does not yet expose the website’s point-funded task or People tools. Use Work, Fast mode or the relevant marketplace API for those flows. The current delegated watch is limited to Venus USDT on BNB testnet with unaudited contracts.
Protect the local wallet
The client uses AIKI_PRIVATE_KEY if configured, otherwise a key stored at ~/.aiki/key. create_wallet writes a new key there with owner-only file permissions. Sign-in sends a SIWE message and signature to the API, not the private key. Do not paste a private key into an assistant conversation.
