Skip to main content
Glama
ZachDreamZ

agent-api-gateway-mcp

by ZachDreamZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to agent-api-gateway-mcp

No user-submitted related servers found.

    Related Servers

    • agent-api-gateway-mcp

      ZachDreamZ
      F
      license
      Not graded
      quality
      A
      maintenance
      Structured web extraction MCP server for AI agents. URL + schema to validated product/article/company JSON via Agent API Gateway. Install with npx -y agent-api-gateway-mcp.
      -

    • extrapify

      christ0pper
      A
      license
      A
      quality
      D
      maintenance
      Structured web context infrastructure for AI agents. Extract reliable schema-guided JSON from websites using Claude-powered parsing, Browserless fallback rendering, and MCP-native workflows.
      1
      1
      MIT

    • singlefile-mcp

      kwinsch
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for intelligent web content extraction from JavaScript-heavy sites using single-file and trafilatura. It enables AI agents to fetch, render, and paginate through clean article content and metadata.
      20
      MIT

    • mult-fetch-mcp-server

      lmcc-dev
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.
      5
      27 npm
      15
      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

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each extraction tool targets a distinct entity (product, article, company), and the administrative tools (list_schemas, get_usage) serve different purposes. No overlap or ambiguity exists.

    Naming Consistency4/5

    Extraction tools follow a consistent 'extract_<entity>' pattern. The administrative tools use different verb prefixes ('list_', 'get_') which is acceptable given their distinct roles, though slightly deviates from the main pattern.

    Tool Count5/5

    With 5 tools covering extraction, schema listing, and usage tracking, the count is well-scoped for an API gateway. No tools feel redundant or missing.

    Completeness4/5

    The set covers common extraction needs and provides schema and usage information. However, it lacks tools for managing schemas (create/update/delete) or extracting additional entity types, which would make it more complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources