contextium-mcp-server
OfficialRelated Servers
Alternatives to contextium-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that gives AI coding agents on-demand access to private project docs via BM25 ranked search. One setup for Claude Code, Cursor, Codex, Gemini CLI, and more. Docs stay private, never in public repos.1515Apache 2.0
- AlicenseNot gradedqualityBmaintenanceStandardize Context, Not Intelligence. An open protocol and native MCP server for preserving, organizing, and serving structured project context (architecture, decision logs, domain rules, and roadmap) to AI coding assistants (Cursor, Claude Desktop, Antigravity) with built-in CLI verificationMIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that provides a shared context and learning foundation across multiple AI tools (Claude, Copilot, Codex) for multiple projects, enabling persistent knowledge, decisions, and gap reflection through note storage.MIT
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that provides up-to-date documentation for enterprise and development tools directly to AI coding assistants like Claude Code and Cursor.MIT
- AlicenseCqualityDmaintenanceMCP server for sharing source-backed engineering memory across AI coding clients like Cursor and VS Code.301MIT
- AlicenseAqualityCmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3726 npm6MIT
TDQS
Scored across 67 tools
Several tools are effectively indistinguishable or redundant: create_project and create_plan are exact aliases, generic create/update/list overlap with create_agent, create_resource, list_agents, and other typed tools, and new_project vs manual_project_setup both describe guided setup. The deprecated project tool adds yet another source of confusion.
Lowercase snake_case is used throughout, but naming styles vary widely: generic single-verb CRUD (list, get, create, update, delete), noun-only tools (marketplace, project), reversed share_create/share_list, and product-prefixed names like contextium_status. Aliases such as create_project/create_plan and overlapping generic/specific tools make the pattern unpredictable.
67 tools is far more than a focused MCP server should expose and will overwhelm agent selection and context. The surface bundles many unrelated domains—files, tasks, phases, identities, notifications, sharing, connectors, marketplace, and setup wizards—that should be split into separate servers.
The surface covers substantial lifecycle coverage: CRUD for files, libraries, agents, skills, workflows, identities, tasks, phases, comments, notifications, shares, and connectors. Minor gaps remain, such as no delete_task, no delete_project plan, and no get_comment, but agents can usually work around these.