API reference

Mnema is MCP-native, but everything is also reachable over a plain REST API — so any app, not just AI clients, can read and write your workspace. Two ways in: the MCP endpoint (for agents) and REST (for code).

Authentication

Create an API key in Settings → Developer, then send it as a bearer token:

Authorization: Bearer mnema_api_xxxxxxxxxxxxxxxx

The key is scoped to your workspace and can read and write everything in it.

MCP endpoint

Point any MCP client at:

https://api.theboringpeople.in/mcp

(Self-hosting? Use your own origin, e.g. http://localhost:8080/mcp.)

MCP tools

The MCP server exposes your workspace as tools. The main ones:

Read

search_docs — hybrid (keyword + semantic) search across your workspace
get_doc, get_doc_section — fetch a document or one section
list_docs, list_folders, list_projects — browse
traverse_graph, get_concept_context, get_graph_report — the knowledge graph
list_flows, get_flow, get_flow_run, list_flow_runs — flows
list_project_tasks, get_next_task — tasks

Write

propose_doc_write / confirm_doc_write — create or edit a document (propose → confirm)
create_task, claim_task, complete_task — tasks
create_flow, add_flow_node, connect_flow_nodes — build a flow
start_flow_run, submit_flow_step_result, submit_flow_capture — run a flow
record_decision, log_milestone, log_blocker — capture

REST API

Base URL: https://api.theboringpeople.in

Search

curl https://api.theboringpeople.in/api/search?q=deployment \
  -H "Authorization: Bearer $MNEMA_KEY"

Create a document

curl -X POST https://api.theboringpeople.in/api/docs \
  -H "Authorization: Bearer $MNEMA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Release notes","markdown":"# v0.1 ..."}'

Every endpoint requires the bearer token above. Requests without a valid key return 401.