A
licenseB
qualityD
maintenanceMCP server for Contextium — pipe team SOPs, coding standards, agents, skills, and workflows directly into Claude, Cursor, and other AI
coding assistants.
67
MIT
@uselink/mcp
by c0x12c
Related Servers
Alternatives to @uselink/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.24 npmMIT
mcp-lindoaiofficial
AlicenseBqualityBmaintenanceMCP (Model Context Protocol) server for Lindo AI — create websites, pages, and blog posts with AI directly from Claude, Cursor, Kiro, Windsurf, and other MCP-compatible tools.50139 npm3MIT
Cactus MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceConnects MCP clients such as Claude, ChatGPT, Cursor and VS Code to a product's published help pages, product map, release timeline and past support conversations, letting users search, read, ask questions with cited answers, and run code-backed investigations. It also offers a sign-in-free server per public help center for visitor-style help search and team contact.MIT- AlicenseAqualityDmaintenanceMCP server for integrating Confluence with AI agents, enabling search, read, and retrieval of documentation, plus syncing and pushing markdown files.7395 npmMIT
- AlicenseAqualityCmaintenanceMCP server for AI-powered image, audio, and video generation, enabling media creation directly from Claude, Cursor, and other MCP clients.1143 npmMIT
TDQS
B3.4/5.0
Scored across 34 tools
Disambiguation3/5
Most tools are distinct, but uselink_search_documents is a thin wrapper over uselink_list_documents, and uselink_rename_project_slug duplicates slug updating via uselink_update_project. uselink_publish_with_assets also overlaps with the create+upload+publish workflow, creating mild selection ambiguity.
Naming Consistency5/5
Every tool follows a consistent uselink_<verb>_<noun> pattern in lowercase snake_case. Verbs clearly indicate actions (list, create, update, publish, delete) and resources are consistent across documents, projects, folders, comments, and assets. There is no stylistic mixing.
Tool Count2/5
At 34 tools, the surface is heavy. While the domain spans multiple resources, the count is inflated by redundant conveniences (search vs list, rename vs update, publish_with_assets) and exceeds the recommended range for a coherent toolset.
Completeness3/5
Core document (CRUD + publish/unpublish), project, and folder management are well covered. However, comments lack a create tool—only list, reply, and resolve—so new threads cannot be started. Also missing are comment deletion or unresolve and asset deletion, which are notable gaps for a collaboration platform.
Maintenance
ActivityInactive
ResponsivenessNo issues