Transport
Pick stdio for local clients, SSE for streaming workflows, or HTTP for web deployments that need a stable route.
MCP memory
Plan a Cognee MCP memory server
The upstream MCP server exposes focused remember, recall, and forget tools through stdio, SSE, or Streamable HTTP. Use this page to choose the deployment mode.
Connection mode
Decide whether the MCP server owns Cognee storage directly, connects to an API server, or points clients at a managed Cognee instance.
Client safety
Define dataset names, tenant boundaries, API tokens, logging, deletion expectations, and memory-review controls.
Strong relevance
Keyword intent handled here
These terms are used for page intent because they match the product theme and landing task. They remain keyword candidates until same-request MiroFish Trends evidence is collected.
MCP memory server
Choose transports, client setup, API mode, Docker mode, and memory access controls.
Theme relevance: Directly maps to the MCP memory server landing page and paid planning workflow.
pending_mirofish_value
Cognee MCP memory server
Plan Cognee memory access through MCP clients and transports.
Theme relevance: Exact product and capability match for the MCP landing page.
pending_mirofish_value