A typed knowledge graph
for agents and humans.

Extraction lands as suggested, never as fact. No form, no folder, no type picker — and nothing above changed the original capture.

Six kinds, seven trait bits, one CoreNode. None of them is compiled in — each is a recipe you own. A Trip and an Errand differ by two bits, not by two apps. When a kind grows a trait, cards pick up the chrome automatically — no new UI per type, no migration.

> read_node { "id": "p_8f3a" }

{
  "id": "p_8f3a",
  "core_kind": "note",
  "kind_def": "kind_def::paper",
  "props": {
    "title": "Out of the Tar Pit",
    "doi": "10.1.1.93.8928",
    "venue": "SPA 2006",
    "published_at": "2006-02-06"
  }
}

// cites edges → p_2b71, p_4c09
//   (walk_from, depth 1)

GET /v1/walk?from=p_8f3a&depth=2

{
  "from": "p_8f3a",
  "depth": 2,
  "steps": [
    {
      "depth": 1,
      "edge": { "kind": "cites",
                "to": "p_2b71" },
      "vertex": { "id": "p_2b71" }
    }
  ]
}

// walk_from over MCP hits the same
//   traversal — a typed subgraph,
//   not a similarity blob.

Same ID. Same fields. Same edges. RAG retrieves chunks; a document store recalls pages; Machina returns a typed subgraph the agent can plan against.

External refs live on the linked trait — the mapping is itself graph data, visible on the node. Anything an integration writes back enters as suggested, reviewed like any other ingest. Orchestration never bypasses the trust model.

No app owns the data. Each is a surface over the one engine — what ships is labeled ships; the machina workbench is in design and says so.

1. 01 · engine docker

   # pull and run the engine
   docker run -d \
     --name machina \
     -p 8080:8080 \
     ghcr.io/machina/engine:latest
   
   # verify
   curl localhost:8080/admin/health
   # {"db":"ok"}

2. 02 · mcp server cargo

   # install the MCP bridge
   cargo install machina-mcp
   
   # point it at the local engine
   export MACHINA_ENGINE_URL=\
     http://localhost:8080
   
   machina-mcp --version
   # machina-mcp 0.1.0

3. 03 · client mcp.json

   {
     "mcpServers": {
       "machina": {
         "command": "machina-mcp",
         "env": {
           "MACHINA_ENGINE_URL":
             "http://localhost:8080"
         }
       }
     }
   }

Once it opens, the JSON drops into ~/.config/claude/mcp.json, ~/.cline/mcp.json, or your client's equivalent. Restart the agent, and the machina tools (list_note, read_node, walk_from, …) appear in the next session.

The install mechanism ships today — browse, preview, idempotent install. A public shelf of packs other people publish is the direction, not a feature; nothing about it needs a recompile.

Prices indicative until the hosted plane opens. No card up front; no auto-conversion from free. A Pro tier sits between Solo and Team, and Enterprise beyond — full grid when the hosted plane opens.