Skip to main content
Glama
tonyyang0504

platform-mcp-hub

by tonyyang0504
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to platform-mcp-hub

No user-submitted related servers found.

    Related Servers

    • APIClaw

      nordsym
      A
      license
      A
      quality
      B
      maintenance
      The API layer for AI agents. World's biggest API index with 22,000+ APIs and growing. Agents discover and call APIs at runtime with semantic search, structured metadata, and 18 Direct Call APIs including AI providers.
      14
      349 npm
      8
      MIT

    • 0nMCP

      0nork
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Universal AI API Orchestrator. 850 tools across 53 services under a single MCP interface. Connect Claude, GPT, or Gemini to Stripe, Slack, GitHub, LinkedIn, Cloudflare, Shopify, Twilio, and 46 more via natural language. $0.10/execution, no subscription. Patent Pending.
      149 npm
      5
      -

    • MCP-Enabled Integration

      RachaZayni
      F
      license
      Not graded
      quality
      C
      maintenance
      Unifies CRM and productivity tool APIs behind a single interface, letting AI agents and developers create, update, delete, and list records across Zoho, HubSpot, Odoo, Google Sheets, Gmail, and Google Calendar without handling platform-specific schemas.
      -

    • Bellink MCP Server

      barflotek
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to over 30 business tools like Gmail, Slack, and Airtable through a single unified interface. It enables users to perform actions across multiple platforms using natural language without managing individual API integrations.
      24 npm
      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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: 'me' verifies account credentials, 'search' discovers job postings, and 'get_posting' retrieves a specific posting by ID. There is no overlap or ambiguity between them.

    Naming Consistency3/5

    Names mix styles: 'me' is a noun/pronoun endpoint, 'search' is a bare verb, and 'get_posting' uses a verb_noun pattern. Still readable, but it does not follow a single predictable convention.

    Tool Count4/5

    Three tools is a lean but adequate surface for a read-only job posting integration. It covers discovery, retrieval, and auth; a pagination or facets helper could be useful but is not essential.

    Completeness4/5

    The core read-only workflow is complete: authenticate/verify, search postings, and fetch a posting by ID. No create/update/delete is expected for a third-party platform, though ancillary operations like listing companies or saved searches are absent.

    Resources