Skip to main content
Glama
AlexisLspk

ProxyPI

by AlexisLspk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ProxyPI

No user-submitted related servers found.

    Related Servers

    • qa-probe by LS-SIEM-LLP

      qa-probeofficial

      LS-SIEM-LLP
      A
      license
      A
      quality
      C
      maintenance
      Probes your live API and classifies why each endpoint failed (root cause, evidence, and a calibrated confidence level), exposed over MCP so your AI assistant debugs from evidence instead of guessing. Works with FastAPI, Express, Next.js, tRPC, and GraphQL.
      8
      10 npm
      2
      Apache 2.0

    • API to MCP

      husw725
      F
      license
      Not graded
      quality
      D
      maintenance
      Converts any REST API endpoints into MCP tools, enabling AI clients like Cursor and Claude Desktop to call internal services directly.
      -

    • mcp-api-bridge

      BryceEWatson
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with any REST API through typed, validated MCP tools. Provides a pattern to wrap REST APIs as MCP servers.
      MIT

    • mcp-proxy

      dyy-fq
      A
      license
      Not graded
      quality
      C
      maintenance
      Bridges LLM clients with existing RESTful microservices by converting MCP tool calls into REST requests, enabling any REST API to be used as an MCP tool without modifying the microservices.
      486,710 npm
      1
      MIT

    • MCPify

      wycats
      F
      license
      Not graded
      quality
      D
      maintenance
      A dynamic proxy that converts OpenAPI Specification (OAS) endpoints into Message Communication Protocol (MCP) tools, allowing AI agents to use existing REST APIs as if they were native MCP tools without manual implementation.
      16
      -
    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/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: send a request, view history, replay a healed request, and clear records. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'proxypi_' prefix plus a simple action verb (request, history, replay, clear), using lowercase snake_case throughout.

    Tool Count5/5

    With 4 tools, the set is compact and well-scoped for a proxy request healer. Each tool earns its place without redundancy or bloat.

    Completeness5/5

    The tool surface fully covers the request-healing lifecycle: sending, reviewing history, replaying, and clearing records. There are no obvious dead ends or missing operations for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources