Cognitia AI

Consumer AI Memory Layer

View on cognitia-ai.com

Documentation

Cognitia AI

ProductMemory LayerDevelopersFor BusinessesDocsFAQ

Build your memory

DISTRIBUTION

For developers

Build on the memory layer, not another chat wrapper. Integrate governed user memory via MCP and API — with real consenting users behind every token.

API Access

Read and write memory graph data programmatically to power custom workflows and products.

Open Data Platform

MCP & API

Connect user memory to MCP-compatible clients with scoped permissions and revocable OAuth tokens.

MCP documentation

Docs and Guides

Follow setup guides, integration walkthroughs, and platform references for production workflows.

Open Docs

Public MCP endpoint

Cognitia is a user-authorized memory MCP server. Clients connect over JSON-RPC with OAuth; tools such as unified_memory_agent, memory_as_of, and memory_diff operate on the signed-in user's graph.

https://www.cognitia-ai.com/api/mcp

Directory listings (MCPMarketplace, FindMCP, and similar): submit Cognitia as a memory MCP server using the endpoint above and the OAuth flow below. Prefer production tool names — do not invent parallel get_entities-style aliases for listings.

Directory submission checklist

1. Endpoint: https://www.cognitia-ai.com/api/mcp

2. Auth: OAuth at /api/mcp/oauth/* (see consent flow below)

3. Category: user memory / personal knowledge graph

4. After listing goes live, add the public URL here and in docs/roadmap/mcp-directory-listings.md

Live directory URLs: none published yet (Q3 P1). Update this section when MCPMarketplace / FindMCP listings are verified.

Third-party developer access model

Cognitia supports third-party access through MCP OAuth consent and authenticated MCP API calls. Apps do not get blanket access. Each client is registered, users approve scopes, and tokens can be revoked.

  • Register an OAuth client via POST /api/mcp/oauth/register.
  • Redirect users to Cognitia consent at /mcp-authorize with PKCE parameters.
  • Call MCP endpoints after consent using access tokens: POST /api/mcp/tools/list and POST /api/mcp/jsonrpc.
  • Let users review or revoke app access through /api/mcp/oauth/connected-apps.

Integration architecture

End-to-end flow for a third-party app accessing Cognitia memory with explicit user approval.

Step 1

Client Register

App registers OAuth metadata and redirect URIs.

POST /api/mcp/oauth/register

Step 2

User Consent

User reviews requested tools and approves access scopes.

/mcp-authorize

Step 3

Tool Discovery

App uses access token to fetch available tools for the user.

POST /api/mcp/tools/list

Step 4

Memory Operations

App executes memory-aware calls through JSON-RPC.

POST /api/mcp/jsonrpc

Quickstart: first 10 minutes

    1. Register OAuth client with redirect URI.
    1. Redirect user to consent with PKCE.
    1. After consent, call MCP tools list.
    1. Execute memory-capable tool calls via JSON-RPC.
    1. Support revocation in connected apps management.

Example client registration:

curl -X POST https://www.cognitia-ai.com/api/mcp/oauth/register
-H "Content-Type: application/json"
-d '{ "client_name": "My MCP Client", "redirect_uris": ["https://myapp.com/oauth/callback"], "grant_types": ["authorization_code", "refresh_token"], "token_endpoint_auth_method": "none" }'

Example tools discovery call with bearer token:

curl -X POST https://www.cognitia-ai.com/api/mcp/tools/list
-H "Authorization: Bearer <access_token>"
-H "Content-Type: application/json"
-d '{}'

Access patterns

Build against Cognitia memory

Use MCP OAuth and JSON-RPC to query tools and invoke memory-capable operations for your users.

Connect external MCP servers

Use the MCP marketplace flow to connect third-party servers via remote transport or OAuth-based setup.

Product surfaces

Memory LayerContext retrievalMCP & API

Build your memoryView Consent ScreenView Documentation