Skip to main content
Glama
gallanoe

PTC-MCP

by gallanoe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to PTC-MCP

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
      -

    • MCP Proxy

      lizTheDeveloper
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables dynamic loading, hot-reloading, and orchestration of MCP servers without restarting Claude Code, allowing programmatic tool calling and workflow automation across multiple servers.
      2
      -

    • 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
      -

    • SkillStrata

      mirabilitum
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables automatic discovery and reuse of tools from Claude Code execution traces. Provides MCP tools that are distilled from real work, allowing you to reuse previously written scripts without manual effort.
      -

    • Code Executor MCP Server

      aberemia24
      A
      license
      Not graded
      quality
      D
      maintenance
      Universal MCP server for executing TypeScript and Python code with progressive disclosure, reducing token usage by 98% by enabling on-demand access to all other MCP tools through code execution rather than loading tool definitions directly.
      9 npm
      130
      MIT
    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

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clearly defined singular purpose of executing Python programs with MCP integration.

    Naming Consistency5/5

    The single tool follows a clear verb_noun naming pattern (execute_program). Since there are no other tools to compare against, consistency is inherently perfect.

    Tool Count2/5

    One tool is too few for a server's apparent purpose of program execution with MCP integration, as it lacks complementary tools for tasks like listing available programs, managing execution environments, or handling errors. This feels thin and incomplete for the domain.

    Completeness2/5

    The tool surface is severely incomplete for the inferred domain of program execution and MCP tool orchestration. There are obvious gaps, such as no tools for program management, debugging, or result handling, which will limit agent capabilities and cause failures in complex workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources