Adaptive Recall MCP Server

Connect Adaptive Recall to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Adaptive memory system for AI applications. Multi-strategy retrieval, cognitive scoring, knowledge graph, and self-improving ML. Connects via MCP or REST API. The adaptive recall mcp server is what makes that connection.

What the server does

Adaptive Recall is a hosted memory server that stores, retrieves, and manages long-term memory for AI applications. It connects via MCP or REST API.

• Multi-strategy retrieval — four search strategies run in parallel (vector similarity, temporal recency, full-text keyword, knowledge graph traversal) and the system learns which to prioritize for each type of query
• Cognitive scoring — results ranked using ACT-R activation modeling from cognitive science, factoring in recency, access frequency, entity connections, and validated confidence
• Knowledge graph — entities and relationships extracted automatically from stored memories, used as a retrieval pathway alongside text similarity
• Memory lifecycle — memories progress through stages, gain or lose confidence based on corroborating evidence, and fade naturally when unused
• Self-improving — ML models train on your usage patterns, every parameter change must pass statistical validation against real query history before being adopted
• Retrieval quality monitoring — the system verifies its own retrieval consistency and identifies knowledge gaps

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: YOUR_SERVER_URL, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by aiappsapi; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.