Karpathy Guidelines MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_guidelinesA | Returns the full Karpathy coding guidelines. Call this before writing or reviewing code to load the behavioral rules. |
| review_codeB | Review code against the 4 Karpathy principles: Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution. |
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 2 tools
The two tools have distinctly different purposes: one retrieves guidelines, the other reviews code. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern (get_guidelines, review_code), making naming predictable and clear.
Only two tools is minimal but sufficient for the focused domain of guideline retrieval and code review. It is borderline but acceptable.
The server covers its stated purpose completely: retrieving the full guidelines and reviewing code against them. No obvious gaps.