Coding Guides is an MCP server published by io.github.delian, hosted at codeguide-mcp-86057491046.europe-west1.run.app. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 1 tool, including get_guide.
Coding guidelines and best-practice guides for 130+ languages, frameworks, and tools.
126 connections through 5 shared values. Tap any node.
Get the content of a specific coding guide.
| Parameter | Type | Description |
|---|---|---|
| guide_name * | string |
{
"name": "get_guide",
"description": "Get the content of a specific coding guide.",
"inputSchema": {
"type": "object",
"title": "get_guideArguments",
"required": [
"guide_name"
],
"properties": {
"guide_name": {
"type": "string",
"title": "Guide Name"
}
}
},
"outputSchema": {
"type": "object",
"title": "get_guideOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
# Codeguide MCP Server This MCP server provides **mandatory** coding guidelines and best practices. The guides define coding standards that **must be followed** when writing, reviewing, or modifying code. ## Read on principle: the workflow guide Before starting **any non-trivial task** (3+ steps, a new module/algorithm, a refactor, or any behavior change), fetch and apply **`guides://agentic-workflow.md`** as a standing instruction — read it *on principle*, not only when asked. It is the canonical owner of **how you work**: plan-first and re-plan on drift, subagent use and parallel **git-worktree isolation**, the lessons-learned loop (read `docs/lessons.md` before, record corrections after), verification-before-done with an independent second-model **rubber-duck review**, task/checkbox + changelog + docs tracking, configurable constants, and externalized LLM prompts. The language/framework/tool guides govern *what* you write; `agentic-workflow.md` governs *how*. A project's own `CLAUDE.md` / `AGENTS.md` / `CLAUDE.local.md` are authoritative and override it where they differ. ## When to Use **Before writing or modifying code**, fetch the relevant guides for the project's languages, frameworks, and tools. Apply their standards as mandatory rules — not optional suggestions. Typical triggers: - Starting a new coding task or feature - Reviewing or refactoring existing code - Setting up a new project - When the user asks about coding standards or best practices - When there is an explicit request --- ## How to Use This Server (MCP Client) The server exposes **resources** and **one tool**. Use standard MCP operations: **ListResources**, **ListResourceTemplates**, **ReadResource**, **ListTools**, and **CallTool**. ### Step 1: Discover guides (always do this first) - **Read the resource** with URI **`guides://list`**. - This returns a text list of all available guides. - Each line has the form: `guide_name.md - brief description` - Use this list to choose which guides apply to the project (e.g. `python.md`, `rest.md`, `dockerfile.md`). Alternatively, you can use **ListResources** to see that `guides://list` is available, and **ListResourceTemplates** to see that `guides://{guide_name}` is available. ### Step 2: Get full content for each guide you need For each selected guide, get its full content using **either**: - **ReadResource** with URI **`guides://{guide_name}`** Example: read resource **`guides://python.md`** (use the exact filename from the list, including `.md`). - **CallTool** with tool name **`get_guide`** and arguments **`{"guide_name": "guide_name.md"}`** Example: call tool **`get_guide`** with **`{"guide_name": "python.md"}`**. Both return the full markdown content of the guide. Use one or the other; no need to use both for the same guide. ### Step 3: Follow references (MANDATORY) Guides are deliberately small: they do **not** duplicate shared content. Instead they **reference** other guides that own a cross-cutting concern (TDD, hexagonal architecture, secure coding, error handling, logging, configuration, etc.). You **MUST** follow those references — a guide is incomplete without them. When a guide you fetched contains a reference marker, act on it: - **📎 REQUIRED** — You **MUST** fetch and apply the linked guide **before writing any code**. It is a hard prerequisite; the referencing guide assumes its rules and does not restate them. Skipping it means you are violating mandatory standards. - **📎 RECOMMENDED** — You **MUST** fetch and apply the linked guide **if the current task touches that concern** (e.g. fetch `logging.md` when the task involves logging). - **📎 SEE ALSO** — Optional; fetch for additional depth when useful. Reference targets appear as `guides://<name>.md` links (e.g. `guides://tdd.md`). Resolve each one with **ReadResource** or the **`get_guide`** tool, exactly as in Step 2. Follow references **transitively** — if a referenced guide has its own REQUIRED references
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.