Skip to main content
Glama
ajbisht

OpenCodeMode

by ajbisht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to OpenCodeMode

No user-submitted related servers found.

    Related Servers

    • MCP Code Mode

      hoangnb24
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to write and execute Python code in an isolated sandbox that can orchestrate multiple MCP tool calls, reducing context window bloat and improving efficiency for complex workflows.
      23
      -
    • Model Context Shell by StacklokLabs

      Model Context Shellofficial

      StacklokLabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to compose MCP tool calls into Unix-style pipelines, executing complex workflows server-side and returning only the final result.
      22
      Apache 2.0

    • codemode-node

      a-saeedia
      A
      license
      A
      quality
      A
      maintenance
      Enables agents to accomplish multi-step work by writing a single sandboxed JavaScript program that drives shell, filesystem, HTTP, and every tool of any configured MCP server, returning only a small summary instead of raw JSON. This collapses dozens of advertised tool schemas into one tool, cutting per-request context by roughly 26× while keeping disabled upstream servers reachable.
      1
      MIT

    • fde-assessment

      BalajiPillalamarri
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP tool calls with strict schema validation and stdio isolation, while providing a security gateway for tool-level authorization, streaming PII redaction, and model failover routing.
      -

    • code2mcp

      blas0
      F
      license
      A
      quality
      Not graded
      maintenance
      Enables execution of TypeScript code to call MCP tools instead of direct tool calls, reducing token usage by up to 98% while orchestrating complex multi-tool workflows through secure sandboxed code execution.
      1
      -
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: execute_code runs TypeScript/JavaScript in a sandbox, while get_tool_types returns the downstream TypeScript declarations. An agent can easily tell which tool to use for execution versus discovery.

    Naming Consistency5/5

    Both names follow a consistent snake_case verb_noun pattern: execute_code and get_tool_types. There is no mixing of conventions or vague naming.

    Tool Count4/5

    Two tools is minimal, but for a meta-execution server this surface is well-scoped: one tool discovers downstream APIs and the other executes code against them. It is slightly thin by typical MCP standards but reasonable for the stated purpose.

    Completeness4/5

    The pair covers the core lifecycle of discovering downstream tool types and executing orchestration code against them. Minor gaps exist around richer discovery or validation, but the essential workflow has no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources