Advertise
MCP.so
Sign In

Crosmos MCP Server

@crosmos-labs

Repository

Basic information

Category

Memory & Knowledge

Transports

stdio

Author

crosmos-labs

Submitted by

Aditya Chaudhary

About Crosmos MCP Server

Persistent memory for AI agents. Give your coding assistant organizational context that compounds — search memories with hybrid retrieval, store anything with auto entity extraction, and query a living knowledge graph that gets smarter over time.

#context#ai#memory

Crosmos MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "crosmos-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@crosmos/crosmos-mcp"
      ],
      "env": {
        "CROSMOS_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Crosmos MCP Server tools

4

Search memories in Crosmos Memory Engine using hybrid retrieval. Combines semantic (vector), keyword (full-text), and graph-based retrieval. Requires a space_id — call list_spaces if you don't have one yet.

Add new memories to Crosmos Memory Engine. Content is processed through an extraction pipeline that identifies entities, relationships, and creates structured knowledge graph entries. Requires a space_id — call list_spaces if you don't have one yet.

Check the health status of the Crosmos Memory Engine API

List all memory spaces owned by the authenticated user. Call this to discover available space IDs needed by search_memories and add_memory.

Overview

What is Crosmos?

Crosmos is a persistent memory layer for AI agents. It enables agents to store and retrieve organizational knowledge across sessions using a temporal knowledge graph with hybrid retrieval.

How to use Crosmos?

Install via npx @crosmos/crosmos-mcp setup which auto-detects MCP clients, or configure manually with a JSON block setting the CROSMOS_API_KEY (obtainable at console.crosmos.dev). Supported clients include Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, opencode, Cline, Roo-Cline, and Zed.

Key features of Crosmos?

  • Graph-native memory with entity and relationship linking
  • Temporal – every fact is timestamped for time‑travel queries
  • Hybrid retrieval (semantic, keyword, graph, temporal)
  • Automatic entity and relationship extraction from raw text
  • Multi‑space isolation for projects, teams, or agents
  • Four retrieval signals fused into a single ranked result

Use cases of Crosmos?

  • Store and retrieve organizational knowledge across AI agent sessions
  • Query the knowledge graph as it existed at any past point in time
  • Isolate memory by project, team, or agent using named spaces
  • Allow agents to maintain persistent context without resets
  • Enable hybrid search combining semantic meaning with graph traversal

Frequently asked questions

1

What is Crosmos and how does it differ from flat vector databases?

Crosmos uses a temporal knowledge graph that links memories as entities and relationships, not just flat vectors, enabling richer context and time

Comments

More Memory & Knowledge MCP servers

AOCI-CODE

aoci-spec

Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.

1.7K

server-noonien - shared memory MCP

sequico

Shared, serverless, conflict-free memory for AI agents: a multi-machine drop-in for the MCP memory knowledge graph.

Neither MCP

stonianua

Project context your AI can query through MCP — with source evidence.

UmmahAPI

Yousuf Kazmi

Islamic source data for assistants: Quran, hadith, tafsir, duas, prayer times and qibla. Answers come from real sources with citations instead of recalled text, so verses and hadith are not hallucinated. 36,000+ hadiths

Agimem

Persistent memory for AI agents. Hosted MCP server with capsule-scoped key/value storage, tags, TTL expiration, bulk ops, and RBAC.

Advertise