Skip to main content
Glama
torshepherd

Compiler Explorer MCP

by torshepherd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Compiler Explorer MCP

  • ce-analyzer-mcp

    Malkovsky
    A
    license
    A
    quality
    A
    maintenance
    A bounded MCP server for C++ analysis through Compiler Explorer, providing compiler discovery, compilation, assembly comparison, analyzers, and shortlink sharing.
    9
    MIT

Related Servers

  • MCP Python Interpreter

    PortPro-Technologies-Inc
    F
    license
    A
    quality
    Not graded
    maintenance
    A Model Context Protocol server that allows LLMs to interact with Python environments, enabling code execution, file operations, package management, and development workflows.
    9
    -

  • CPPCon MCP Server

    zzuse
    F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables users to compile C++ code and retrieve assembly output through the Compiler Explorer (godbolt.org) API. It supports standard tool calls and Server-Sent Events for streaming compilation status and results.
    -

  • Binary Ninja MCP Server

    rsprudencio
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables Large Language Models to interact with Binary Ninja for reverse engineering tasks like viewing assembly code, decompiled code, renaming functions, and adding comments.
    3
    MIT

  • PAL MCP

    ramarivera
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a distinct, non-overlapping purpose: compile_code handles compilation, get_opcode_documentation provides opcode docs, list_compilers_for_language lists compilers by language, list_compiler_versions lists compiler versions, and list_languages lists supported languages. There is no ambiguity in tool selection.

Naming Consistency4/5

Tools follow a consistent verb_noun pattern (compile_code, get_opcode_documentation, list_compilers_for_language, list_compiler_versions, list_languages), all using snake_case. The minor deviation is that get_opcode_documentation uses 'get' while others use 'list' or 'compile', but this is appropriate for its action and doesn't break consistency.

Tool Count5/5

With 5 tools, this is well-scoped for a compiler exploration server. Each tool serves a clear purpose in the workflow (listing languages/compilers, compiling code, getting documentation), and none feel redundant or missing given the domain.

Completeness4/5

The toolset covers core compiler exploration tasks: listing languages and compilers, compiling code, and accessing opcode documentation. A minor gap is the lack of tools for managing compilation sessions or saving/loading code snippets, but the provided tools enable basic compilation and exploration workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources