mcpField
A
aurekai-mcp

aurekai-mcp

Local
github.com/aurekaiDeveloper Tools0Updated 26w ago

About aurekai-mcp

aurekai-mcp maps Aurekai capability families to MCP tools for developers and agents inspecting runtime state, artifacts, and features. It also provides resources, pagination, and named prompts.

Key features

  1. 01Covers 9 capability families
  2. 02Provides 89 operator tools
  3. 03Reads runtime, queue, and model resources
  4. 04Supports resource pagination and subscription acknowledgements
  5. 05Includes 8 named prompts
  6. 06Propagates proof metadata and embedded resources

Use cases

  1. 01Inspect Aurekai runtime and queue status
  2. 02Trace an artifact's Merkle lineage
  3. 03Turn audio into a brief or deliverable
  4. 04Validate a release gate and manifest

MCP support

Exposes Aurekai capabilities as MCP tools, resources, and prompts over stdio or Streamable HTTP. Tools require `akai` on PATH or a binary specified through `AKAI_BIN`.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"aurekai-aurekai": {
"command": "npx",
"args": [
"-y",
"@aurekai/mcp"
]
}
}
}
Run commandnpx -y @aurekai/mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@aurekai/mcp0.8.0-alpha.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Aurekai

@aurekai/mcp — Aurekai MCP Server

0.8.0-alpha.5 · capability-native · zero dependencies · stdio + Streamable HTTP

Exposes all 9 Aurekai capability families (111 commands) as MCP tools with full protocol-level features: tool annotations, resource pagination, named prompts, _meta proof propagation, and embedded resource outputs.

Install

npm install -g @aurekai/mcp

Usage

stdio (default — for Claude Desktop, Cursor, etc.)
// claude_desktop_config.json
{
  "mcpServers": {
    "aurekai": {
      "command": "aurekai-mcp"
    }
  }
}
Streamable HTTP (optional)
AKAI_MCP_HTTP_PORT=3100 aurekai-mcp
# POST JSON-RPC to http://127.0.0.1:3100/mcp

Protocol Surface

FeatureStatus
tools/list — 89 operators across 9 capability families✅
Tool annotations (readOnlyHint, destructiveHint, idempotentHint)✅
resources/list — 13 aurekai:// resource URIs✅
resources/read — live reads for runtime/capabilities, queue/stats, models✅
Resource pagination (nextCursor)✅
Resource subscriptions (acknowledge)✅
prompts/list + prompts/get — 8 named capability prompts✅
_meta proof propagation on tool call results✅
Embedded resource outputs for proof-emitting tools✅
logging server capability✅
Streamable HTTP transport (AKAI_MCP_HTTP_PORT)✅

Capability Families

FamilyOperatorsExamples
runtime11akai_api, akai_queue, akai_workflow
commerce11akai_gate, akai_pay, akai_ledger
intake12akai_transcribe, akai_ingest, akai_segment
memory11akai_fpq, akai_fpqx, akai_embed, akai_vec
proof8akai_proof, akai_canon, akai_graph, akai_hash
reason5akai_reason, akai_physics, akai_flow, akai_learn
wire5akai_tel, akai_wire, akai_moq, akai_net
publish9akai_brief, akai_narrate, akai_pack, akai_distribute
substrate17akai_capability, akai_space, akai_compress

Named Prompts

PromptDescription
turn-this-call-into-a-deliverableaudio → transcribe → brief → deliverable
inspect-this-artifact-lineageResolve full Merkle lineage for an artifact
build-a-model-memory-packFPQ compress + roundtrip + export memory pack
compare-these-reasoning-branchesDual branch diff with recommendation
generate-client-invoice-from-usageMetering records → invoice
produce-wire-device-reportPCAP → SIP event + device report
run-a-release-gateproof validate + manifest verify + SLI auto-run
make-a-client-brief-from-this-audioaudio → transcript → structured client brief

Resources (aurekai:// URIs)

aurekai://runtime/capabilities · aurekai://queue/stats · aurekai://ledger/portfolio aurekai://models · aurekai://model-memory · aurekai://features/{artifact} aurekai://proof/{id} · aurekai://graph/{node}/lineage · aurekai://space/{name} aurekai://wire/{capture_id} · aurekai://project/{id} · aurekai://invoice/{id} · aurekai://cms/{entry_id}

Runtime Requirement

Tools require the akai binary on PATH (from aurekai/native-runtime) or set AKAI_BIN=/path/to/akai. Without it, tools return a clear error message — no crash.

Registry Targets

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.