A
licenseNot graded
qualityD
maintenanceProduction-ready TypeScript template for building MCP servers. Works with Claude Code, Cursor, and any MCP client.
11 npm
1
MIT
@furkankoykiran/coderlegion-mcp
Related Servers
Alternatives to @furkankoykiran/coderlegion-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityFmaintenanceA TypeScript-based MCP server designed for experimentation and integration with Calude Desktop and Cursor IDE, offering a modular playground for extending server capabilities.2318 npm7MIT
- AlicenseAqualityAmaintenanceProduction-ready template for building MCP servers with TypeScript, featuring example tools and resources, and Claude Desktop integration.110 npmMIT
- AlicenseNot gradedqualityCmaintenanceProxy MCP server that translates tool calls into TypeScript code generation, enabling LLMs to orchestrate multi-tool workflows efficiently via code.12 npm14MIT
- AlicenseAqualityDmaintenanceA TypeScript MCP server that gives text-only LLMs image understanding through StepFun vision models.71,150 npmMIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript template for building MCP servers, enabling developers to create custom tools for AI assistants like Claude.25 npmMIT
TDQS
A3.5/5.0
Scored across 14 tools
Disambiguation4/5
Most tools target a distinct action+resource, but the read-side of posts has four overlapping entry points (list_posts, search_posts, browse_tag, get_activity_feed) that an agent could easily confuse when just wanting to find posts. The descriptions do differentiate them (by user, query, tag, followed users), so ambiguity is manageable rather than severe.
Naming Consistency5/5
Every tool follows a clean verb_noun snake_case pattern (get_post, create_post, edit_post, delete_post, add_comment, react_to_post, get_profile, edit_profile). No mixed conventions or vague verbs appear anywhere in the set.
Tool Count5/5
14 tools is well within the sweet spot for a social/blogging platform and each one maps to a real user-facing operation. Nothing feels padded or redundant at the count level.
Completeness4/5
Posts have full lifecycle coverage (create, get, list, search, browse, edit, soft-delete) plus comments, reactions, categories, profile, notifications, and a feed. Minor gaps exist on the secondary resources — no delete/unreact for reactions, no comment listing or deletion — but these are workable omissions.
Maintenance
ActivityInactive
ResponsivenessNo issues