Cognitia AI
DISTRIBUTION
MCP & API
Take your memory to any MCP client — Claude Desktop, Cursor, or custom agents. Your graph stays portable; access stays permissioned.
How it works
- Authorize external services through scoped permissions.
- Allow services to read or write memory based on your consent settings.
- Use connected context to improve personalization across tools.
- Review and revoke approvals at any time.
Example workflow
You begin planning in Cognitia, then continue execution in a connected MCP-capable tool. The external service receives only approved context, enabling continuity while preserving your control over data access.
How third-party developers access Cognitia memory
- Register the client for OAuth and define redirect URLs using POST /api/mcp/oauth/register.
- Start user consent with PKCE and redirect to /mcp-authorize so users choose allowed tools and data scopes.
- Call authenticated MCP endpoints: POST /api/mcp/tools/list to discover tools and POST /api/mcp/jsonrpc to execute calls.
- Support revocation and lifecycle management through /api/mcp/oauth/connected-apps.
Server connectivity paths
- Remote MCP servers: connect directly from the marketplace.
- OAuth-required servers: initiate with /api/mcp-servers/oauth/initiate and complete callback at /api/mcp-servers/oauth/callback.
- Local-only servers: install through daemon-backed marketplace flow.
Permissions and endpoint matrix
Third-party apps should request only the minimum permissions needed for each workflow.
| Permission / Tool | Typical Purpose | Primary Endpoint | Execution Method |
|---|---|---|---|
| lookup_entities | Primary read for named people/orgs — relationships + linked facts (use first even for “latest about X”) | /api/mcp/jsonrpc | tools/call via unified_memory_agent (lookup_entities) |
| search_temporal | Subject-less / global time windows (“what changed last week?”) — not first tool when an entity is named | /api/mcp/jsonrpc | tools/call via unified_memory_agent (search_temporal) |
| get_user_profile | Get preferences, habits, goals, and current situation | /api/mcp/jsonrpc | tools/call via unified_memory_agent (get_user_profile) |
| store_knowledge | Store new memory with user consent | /api/mcp/jsonrpc | tools/call via unified_memory_agent (store_knowledge) |
| search_emails / search_files / search_app_sync / … | Per-source consent for indexed data (emails, cloud files, local app sync, ambient, …) | /api/mcp/jsonrpc | Capability toggle — agent searches via search_memory_vectors within the allowlist |
| search_memory_vectors | Unified semantic search over enabled sources only (optional sources filter) | /api/mcp/jsonrpc | tools/call via unified_memory_agent (runtime tool; not a consent key) |
| get_memory_artifact | Hydrate full raw artifact after a vector hit | /api/mcp/jsonrpc | tools/call via unified_memory_agent (runtime tool; allowlist enforced) |
| tools/list | Discover available tools for token | /api/mcp/tools/list | POST with Bearer token |