Code-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port number for the server | 3000 |
| CODE_MCP_API_KEY | No | Optional API key for authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sequential_thinkingB | A tool to facilitate sequential, structured thinking. It forces the AI to break down complex problems into steps, validating each before moving to the next. Use this when facing a complex coding task or architectural decision. |
| plan_taskA | Creates a structured plan for completing a coding task. Breaks down the work into steps with dependencies, validation criteria, and estimated complexity. Use before starting any significant coding work. |
| reflect_on_codeB | Provides a structured critique of code, analyzing quality, security, performance, and maintainability. Returns specific improvement suggestions. |
| analyze_architectureB | Analyzes system architecture, identifying patterns, potential issues, and improvement opportunities. Use for design reviews and technical decisions. |
| debug_problemB | Provides a systematic debugging approach for a described problem. Generates hypotheses, test strategies, and resolution steps. |
| brainstorm_solutionsC | Generates multiple solution approaches for a problem, with pros/cons for each. |
| compare_approachesC | Compares multiple technical approaches on various dimensions to help make informed decisions. |
| estimate_complexityC | Estimates the complexity and effort required for a task or feature. |
| generate_testsB | Generates test case suggestions for a feature or function. |
| explain_codeC | Provides a detailed explanation of code, breaking down what each part does. |
| save_memoryA | Save a key-value pair to persistent memory. Use this to remember user preferences, project decisions, or important context across sessions. |
| read_memoryC | Read a value from persistent memory by key. |
| list_memoriesB | List all saved memories, optionally filtered by project scope. |
| clear_memoryC | Clear a specific memory by key, or clear all memories for a project. |
| validate_codeB | Validates code syntax and formatting using available linters (e.g., Prettier). usage: providing code snippets to check for correctness before finalizing. |
| generate_cursor_rulesB | Generates a .cursorrules file for Cursor AI based on the project stack. |
| generate_gemini_configC | Generates a GEMINI.md file for Gemini/Antigravity configuration. |
| generate_claude_configC | Generates a CLAUDE.md file for Claude Projects/Tasks. |
| generate_windsurf_configC | Generates a .windsurfrules file for Windsurf IDE. |
| generate_aider_configC | Generates a .aider.conf.yml file for Aider AI. |
| generate_cline_configC | Generates a .clinerules file for Cline/Roo Code. |
| generate_copilot_configC | Generates a .github/copilot-instructions.md for GitHub Copilot. |
| check_importsC | Checks import statements in code for common issues like circular dependencies, unused imports, and missing modules. |
| lint_codeC | Analyzes code for style issues, potential bugs, and best practice violations. |
| format_codeB | Provides formatted version of code following language-specific style guides. |
| generate_continue_configC | Generates a .continue/config.json file for Continue.dev. |
| generate_tabnine_configC | Generates a .tabnine.json configuration file. |
| generate_vscode_tasksC | Generates a .vscode/tasks.json file for VSCode. |
| generate_vscode_launchC | Generates a .vscode/launch.json file for debugging. |
| generate_jetbrains_configC | Generates a .idea/runConfigurations XML file for JetBrains IDEs. |
| track_projectA | Analyzes and tracks project structure, keeping inventory of all files, folders, and their purposes. Use at project start and after major changes. |
| check_dependenciesB | Analyzes project dependencies for security vulnerabilities, deprecations, and outdated packages. Essential for maintaining healthy projects. |
| generate_github_actionsC | Generates GitHub Actions workflow files for CI/CD, testing, security scanning, and deployment. |
| full_stack_scaffoldB | Generates a complete full-stack project structure with all necessary files and configurations. One command to create a production-ready project. |
| developer_rulesC | Provides comprehensive developer rules and checklists for maintaining high-quality, secure code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| setup_project | Initialize a new project with the optimal stack and configuration |
| act_as_architect | Think like a software architect - focus on system design, scalability, and patterns |
| act_as_debugger | Think like a debugger - systematic root cause analysis |
| act_as_reviewer | Think like a code reviewer - focus on quality, security, and best practices |
| act_as_security_auditor | Think like a security professional - identify vulnerabilities and risks |
| act_as_mentor | Think like a senior developer mentor - teach and guide with patience |
| act_as_devops | Think like a DevOps engineer - focus on automation, reliability, and infrastructure |
| act_as_tester | Think like a QA tester - find bugs, edge cases, and quality issues |
| act_as_optimizer | Think like a performance optimizer - make things fast and efficient |
| write_example_code | Generate practical, production-ready code examples |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Python Coding Rules | Best practices for Python (General Purpose) |
| JavaScript Coding Rules | Best practices for JavaScript (Web) |
| TypeScript Coding Rules | Best practices for TypeScript (Web) |
| Rust Coding Rules | Best practices for Rust (Systems) |
| Go Coding Rules | Best practices for Go (Systems) |
| Java Coding Rules | Best practices for Java (Enterprise) |
| C# Coding Rules | Best practices for C# (Enterprise) |
| C++ Coding Rules | Best practices for C++ (Systems) |
| C Coding Rules | Best practices for C (Systems) |
| Kotlin Coding Rules | Best practices for Kotlin (Mobile) |
| Swift Coding Rules | Best practices for Swift (Mobile) |
| PHP Coding Rules | Best practices for PHP (Web) |
| Ruby Coding Rules | Best practices for Ruby (Scripting) |
| Lua Coding Rules | Best practices for Lua (Scripting) |
| Perl Coding Rules | Best practices for Perl (Scripting) |
| Bash Coding Rules | Best practices for Bash (Scripting) |
| PowerShell Coding Rules | Best practices for PowerShell (Scripting) |
| Haskell Coding Rules | Best practices for Haskell (Functional) |
| Elixir Coding Rules | Best practices for Elixir (Functional) |
| Erlang Coding Rules | Best practices for Erlang (Functional) |
| OCaml Coding Rules | Best practices for OCaml (Functional) |
| F# Coding Rules | Best practices for F# (Functional) |
| Clojure Coding Rules | Best practices for Clojure (Functional) |
| Scala Coding Rules | Best practices for Scala (Functional) |
| Elm Coding Rules | Best practices for Elm (Functional) |
| Racket Coding Rules | Best practices for Racket (Functional) |
| Scheme Coding Rules | Best practices for Scheme (Functional) |
| Common Lisp Coding Rules | Best practices for Common Lisp (Functional) |
| R Coding Rules | Best practices for R (Data Science) |
| Julia Coding Rules | Best practices for Julia (Data Science) |
| MATLAB Coding Rules | Best practices for MATLAB (Data Science) |
| Dart Coding Rules | Best practices for Dart (Mobile) |
| Objective-C Coding Rules | Best practices for Objective-C (Mobile) |
| Zig Coding Rules | Best practices for Zig (Systems) |
| Nim Coding Rules | Best practices for Nim (Systems) |
| D Coding Rules | Best practices for D (Systems) |
| Assembly Coding Rules | Best practices for Assembly (Systems) |
| COBOL Coding Rules | Best practices for COBOL (Legacy) |
| Fortran Coding Rules | Best practices for Fortran (Legacy) |
| Pascal Coding Rules | Best practices for Pascal (Legacy) |
| Ada Coding Rules | Best practices for Ada (Legacy) |
| Groovy Coding Rules | Best practices for Groovy (Scripting) |
| Tcl Coding Rules | Best practices for Tcl (Scripting) |
| AWK Coding Rules | Best practices for AWK (Scripting) |
| SQL Coding Rules | Best practices for SQL (Query) |
| GraphQL Coding Rules | Best practices for GraphQL (Query) |
| Cypher Coding Rules | Best practices for Cypher (Query) |
| HTML Coding Rules | Best practices for HTML (Markup) |
| CSS Coding Rules | Best practices for CSS (Markup) |
| SCSS Coding Rules | Best practices for SCSS (Markup) |
| Sass Coding Rules | Best practices for Sass (Markup) |
| JSON Coding Rules | Best practices for JSON (Config) |
| YAML Coding Rules | Best practices for YAML (Config) |
| TOML Coding Rules | Best practices for TOML (Config) |
| XML Coding Rules | Best practices for XML (Config) |
| Markdown Coding Rules | Best practices for Markdown (Documentation) |
| PostgreSQL Best Practices | SQL RDBMS database patterns |
| MySQL Best Practices | SQL RDBMS database patterns |
| MariaDB Best Practices | SQL RDBMS database patterns |
| SQLite Best Practices | SQL Embedded database patterns |
| Oracle Database Best Practices | SQL Enterprise database patterns |
| SQL Server Best Practices | SQL Enterprise database patterns |
| IBM DB2 Best Practices | SQL Enterprise database patterns |
| MongoDB Best Practices | NoSQL Document database patterns |
| CouchDB Best Practices | NoSQL Document database patterns |
| RavenDB Best Practices | NoSQL Document database patterns |
| Cloud Firestore Best Practices | NoSQL Document database patterns |
| Redis Best Practices | NoSQL Key-Value database patterns |
| Amazon DynamoDB Best Practices | NoSQL Key-Value database patterns |
| Memcached Best Practices | NoSQL Key-Value database patterns |
| Couchbase Best Practices | NoSQL Multi-Model database patterns |
| Apache Cassandra Best Practices | NoSQL Wide-Column database patterns |
| ScyllaDB Best Practices | NoSQL Wide-Column database patterns |
| Apache HBase Best Practices | NoSQL Wide-Column database patterns |
| Google Bigtable Best Practices | NoSQL Wide-Column database patterns |
| Neo4j Best Practices | NoSQL Graph database patterns |
| Amazon Neptune Best Practices | NoSQL Graph database patterns |
| ArangoDB Best Practices | NoSQL Multi-Model database patterns |
| JanusGraph Best Practices | NoSQL Graph database patterns |
| TigerGraph Best Practices | NoSQL Graph database patterns |
| Dgraph Best Practices | NoSQL Graph database patterns |
| CockroachDB Best Practices | NewSQL Distributed SQL database patterns |
| TiDB Best Practices | NewSQL Distributed SQL database patterns |
| YugabyteDB Best Practices | NewSQL Distributed SQL database patterns |
| Google Spanner Best Practices | NewSQL Distributed SQL database patterns |
| VoltDB Best Practices | NewSQL In-Memory database patterns |
| Elasticsearch Best Practices | Search Full-Text Search database patterns |
| OpenSearch Best Practices | Search Full-Text Search database patterns |
| Apache Solr Best Practices | Search Full-Text Search database patterns |
| Meilisearch Best Practices | Search Full-Text Search database patterns |
| InfluxDB Best Practices | Time-Series Time-Series database patterns |
| TimescaleDB Best Practices | Time-Series Time-Series database patterns |
| React Best Practices | Frontend framework for javascript |
| Vue.js Best Practices | Frontend framework for javascript |
| Angular Best Practices | Frontend framework for typescript |
| Svelte Best Practices | Frontend framework for javascript |
| Next.js Best Practices | Full-Stack framework for javascript |
| Nuxt Best Practices | Full-Stack framework for javascript |
| Astro Best Practices | Full-Stack framework for javascript |
| SolidJS Best Practices | Frontend framework for javascript |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/millsydotdev/Code-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server