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 committing, searching, and illuminating over long-term memory, with no SDK integration to write.
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 37 tools covering every core operation:
| Group | Tools |
|---|---|
| Core | commit, sync_commit, search, illuminate |
| 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 |
| Entities | list_entities |
| Operations | list_operations, get_operation, cancel_operation |
| Tags | list_tags |
The four core tools mirror the REST memory operations: commit writes
asynchronously and returns an operation id, sync_commit blocks until the
memory is searchable, search runs fused semantic/lexical/graph/temporal
search, and illuminate synthesizes a reasoned answer across everything the
namespace knows.
Connecting to a specific namespace endpoint exposes 34 of the 37 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 reach MCP clients connected to that namespace. Use it for
read-only integrations (say, search and illuminate only), or to keep
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.