Developers
Three ways other systems talk to Alma.
API — you pull. Read-only keys for querying the knowledge base from your own tools.
MCP — your AI client pulls. Connect Claude Desktop, Claude Code, or Cursor to use Alma’s tools while you work.
Webhooks — Alma pushes. Alma calls your endpoint when something happens.
| You want to | Use |
|---|---|
| Query Memory from a dashboard | API |
| Give Claude Desktop access to Alma | MCP |
| React when a workflow finishes | Webhooks |
API keys and MCP tokens are separate credentials. An API key won’t authenticate an MCP client, and an MCP token won’t work against the API.
Vocabulary
The Console and the public API both say Workflows. MCP tool names are the
exception — they say agent (alma_create_agent, alma_execute_agent).
Access rules apply everywhere
Everything here runs through the same tool access rules as the rest of Alma. An MCP client acting as you can’t call a tool you’re not allowed to call, and a rule you write on a connection applies to API and MCP callers too.