@furkankoykiran/coderlegion-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODERLEGION_PHPSESSID | Yes | PHP session ID - required | |
| CODERLEGION_QA_NOTICED | No | Notice acknowledgement cookie | 1 |
| CODERLEGION_QA_SESSION | Yes | Q2A session cookie - required |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_postC | Create a new post on CoderLegion. Supports Articles, Tutorials, Launches, and Videos. |
| edit_postC | Edit an existing post on CoderLegion |
| get_postA | Read a post from CoderLegion and return its title, content snippet, tags, and author |
| list_postsC | List posts by a CoderLegion user |
| add_commentC | Add a comment to a CoderLegion post |
| delete_postB | Hide (soft-delete) a post on CoderLegion. The post becomes invisible to other users. |
| search_postsC | Search for posts on CoderLegion |
| browse_tagB | Browse posts by tag on CoderLegion |
| get_categoriesA | List all CoderLegion post categories with their IDs |
| react_to_postC | React to a CoderLegion post with a like or love |
| get_notificationsB | Get your CoderLegion notifications |
| get_activity_feedA | Get the CoderLegion social activity feed from followed users |
| get_profileA | Get the authenticated user's CoderLegion profile information |
| edit_profileB | Edit the authenticated user's CoderLegion profile. Only specified fields are updated; others remain unchanged. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
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.
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.
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.
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.