Skip to main content
Glama

Related Servers

Alternatives to Polytomic MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for controlling Fivetran data pipelines. Enables AI assistants to manage syncs, monitor connection status, and control pipelines through natural language.
      15
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for PullPush.ai integration sync engine, providing 43 tools to manage connectors, flows, sync operations, diagnostics, and more through the Model Context Protocol.
      65 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Read-only MCP server for self-hosted Airbyte OSS 1.6.x, enabling monitoring of connections, jobs, and health via public and internal APIs. Optionally supports triggering syncs and canceling jobs.
      9
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      MCP server for managing Nango environments, integrations, connections, and proxy requests. Provides tools for environment checks, integration management, connection handling, Connect sessions, and provider API calls through Nango Proxy.
      28
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
      4
      102 npm
      17
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the HubSpot CRM API with tools for managing contacts, companies, deals, tickets, and CRM workflows. Generated with MCPForge. Sensitive operations can be protected with permissions, audit logs, and approval workflows.
      10 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 32 tools

    Disambiguation4/5

    Tools are well-organized around distinct resources (bulk syncs, syncs, connections, models) with clear action differentiation. Minor overlap exists between 'activate_sync' and 'update_sync' with active parameter, but descriptions clarify their distinct purposes (activation vs. full update).

    Naming Consistency5/5

    Perfectly consistent verb_noun pattern throughout (e.g., create_bulk_sync, get_connection, list_models). All tools use snake_case with clear action prefixes (create, get, list, update, delete, activate, trigger) followed by resource names.

    Tool Count3/5

    32 tools is borderline heavy for a data integration server, though it covers multiple resource types comprehensively. The count feels slightly inflated due to parallel tools for bulk syncs and syncs, but remains manageable given the domain complexity.

    Completeness5/5

    Excellent CRUD/lifecycle coverage for all core resources (connections, models, bulk syncs, syncs). Includes activation, triggering, status checks, execution history, and schema management. No apparent gaps for the data integration domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues