SDKs & tools
MCP server
Give Claude, Cursor, or any MCP client direct access to Illumina memory tools.
Illumina exposes its full memory surface over the Model Context Protocol. Connect an MCP client — Claude Code, Claude Desktop, Cursor, or anything that speaks MCP — and the agent gets first-class tools for retaining, recalling, and reflecting over long-term memory, no SDK integration required.
The server is hosted at api.illumina.sh and authenticates with the same
sub_live_... API keys as the REST API. See MCP setup for
connection details.
The tool surface
The server registers 36 tools covering every core operation:
| Group | Tools |
|---|---|
| Core | retain, sync_retain, recall, reflect |
| Namespaces | list_namespaces, create_namespace, get_namespace, get_namespace_stats, update_namespace, delete_namespace |
| Memories | list_memories, get_memory, clear_memories |
| Documents | list_documents, get_document, delete_document |
| Automations | list_automations, get_automation, create_automation, update_automation, delete_automation, refresh_automation, clear_automation |
| Directives | list_directives, create_directive, delete_directive |
| Communities | list_communities, get_community, build_communities, get_community_status, clear_communities |
| Ontology | get_ontology |
| Operations | list_operations, get_operation, cancel_operation |
| Tags | list_tags |
The four core tools mirror the REST memory operations: retain writes
asynchronously and returns an operation id, sync_retain blocks until the
memory is recallable, recall runs fused semantic/lexical/graph/temporal
search, and reflect synthesizes a reasoned answer across everything the
namespace knows.
Connecting to a specific namespace endpoint exposes 33 of the 36 tools — the
namespace-discovery tools (list_namespaces, create_namespace,
get_namespace_stats) only appear in multi-namespace mode, where every tool
also accepts an optional namespace_id argument for cross-namespace
operations.
Narrowing the tool set
Each namespace has an mcp_enabled_tools configuration field. When set, only
the listed tools are exposed to MCP clients connected to that namespace —
useful for read-only integrations (say, recall and reflect only) or for
keeping destructive tools like delete_namespace out of an agent's reach.
The field is managed through the namespace configuration REST API; the MCP
update_namespace tool cannot change it.