{
"mcpServers": {
"aeqi": {
"command": "aeqi",
"args": ["mcp"],
"env": {
"AEQI_API_KEY": "ak_...",
"AEQI_SECRET_KEY": "sk_..."
}
}
}
}Use aeqi from
any MCP client.
aeqi ships a Model Context Protocol server. Claude Code, Codex, Cursor, and any MCP-aware client get direct access to your TRUST runtime — agents, quests, ideas, events, and the code intelligence graph as first-class tools.
Setup
Get a key pair from your account and your company, then point your MCP client at the aeqi binary.
1. Get keys
Account key: app.aeqi.ai/account → API → ak_…. Company secret: app.aeqi.ai/company → API Keys → sk_….
2. Add to Claude Code
3. Or any generic MCP client
export AEQI_API_KEY=ak_...
export AEQI_SECRET_KEY=sk_...
aeqi mcpOn startup, aeqi mcp authenticates with the platform and connects to your TRUST runtime. Tool calls route directly to your agents.
Tool catalog
Core tools use an action-based pattern: tool(action='…', …). Each tool maps to one of the core TRUST primitives or an adjunct surface.
Primitives
agentshire · retire · list · delegateAgent lifecycle (WHO)eventscreate · list · enable · disable · deleteTriggers and schedules (WHEN)questscreate · list · show · update · close · cancelWork items (WHAT)ideasstore · search · update · deleteKnowledge (HOW)Adjuncts
notesread · post · get · query · claim · release · deleteEphemeral signals and resource lockscodesearch · context · impact · file · stats · indexCode intelligence graphDiscovery
aeqi_projects—Projects with repo paths and prefixesaeqi_primer—Project primer (architecture, rules, build/deploy)aeqi_prompts—Registered skills and workflowsaeqi_status—Live runtime — workers, budget, costs, pending workExample
quests(action='create', project='myproject', subject='Fix login bug')
ideas(action='search', project='myproject', query='authentication patterns')
agents(action='list', status='active')
events(action='create', agent='myagent', schedule='0 9 * * *',
content='Post daily standup summary')Environment
AEQI_SECRET_KEYYes—Company secret key (sk_…)AEQI_API_KEYNo—Account key (ak_…), for analyticsAEQI_PLATFORM_URLNohttps://app.aeqi.aiPlatform URL for key validationSelf-hosted
Without the platform, the MCP server connects to the local daemon over a unix socket at ~/.aeqi/rm.sock. No keys required — just have aeqi start running.