Context MCP

Related Servers

Alternatives to Context MCP

No user-submitted related servers found.

Related Servers

Qdrant MCP Server
Vector Databases Knowledge & Memory RAG Systems
mcandiav
A
license
Not graded
quality
D
maintenance
Enables storing and retrieving information using semantic search with Qdrant vector database. Acts as a memory layer for LLMs to persistently store and semantically search through information and metadata.
Updated a year ago (2025-10-13 03:42 UTC)
Apache 2.0
MCP Context Server
Knowledge & Memory RAG Systems
alex-feel
A
license
Not graded
quality
A
maintenance
Enables persistent multimodal context storage for LLM agents with thread-based scoping, metadata filtering, and hybrid search capabilities.
Updated 12 days ago (2026-09-09 07:23 UTC)
9
Elastic 2.0
membot
Knowledge & Memory Search
evantahler
A
license
Not graded
quality
A
maintenance
Provides a persistent, versioned, and searchable context store for AI agents with local embedding and hybrid search.
Updated 3 months ago (2026-07-04 18:05 UTC)
33 npm
3
MIT
MCP AI Memory
Knowledge & Memory Vector Databases RAG Systems
scanadi
A
license
Not graded
quality
D
maintenance
Enables AI agents to store, retrieve, and manage contextual knowledge across sessions using semantic search with PostgreSQL and vector embeddings. Supports memory relationships, clustering, multi-agent isolation, and intelligent caching for persistent conversational context.
Updated 7 months ago (2026-02-16 10:09 UTC)
16 npm
48
MIT
Kirok
Knowledge & Memory RAG Systems AI & Machine Learning
TadFuji
A
license
A
quality
A
maintenance
Provides persistent, searchable memory for AI agents, enabling them to retain, recall, and reflect on information across conversations.
Updated 11 days ago (2026-09-10 05:24 UTC)
19
17 PyPI
1
MIT
mcp-memory
Knowledge & Memory RAG Systems
oneKn8
A
license
A
quality
D
maintenance
Provides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.
Updated 16 days ago (2026-09-05 15:58 UTC)
4
1
MIT

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored 2026-04-18 06:15 across 6 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Tools are clearly separated into categories: adding context (single vs. batch), deleting context (single vs. batch), querying context, and getting statistics. The descriptions make it immediately clear which tool to use for each operation.

Naming Consistency5/5

Tool names follow a perfectly consistent verb_noun pattern throughout. All tools use snake_case with clear action prefixes (add, delete, get, query) followed by the object (context/stats). Even batch operations maintain the same pattern with '_batch' suffix for consistency.

Tool Count5/5

Six tools is well-scoped for a context management server. Each tool earns its place by covering essential operations: CRUD operations (create, read, delete) with both single and batch variants, plus query and statistics capabilities. No tool feels redundant or missing for the domain.

Completeness5/5

The tool surface provides complete CRUD/lifecycle coverage for context management. It covers creation (add single/batch), retrieval (query), deletion (delete single/batch), and monitoring (stats). There are no dead ends or obvious gaps for the stated purpose of managing a vector database of context/knowledge.