nango-mcp-server
Related Servers
Alternatives to nango-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceModel 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-server475 npm16MIT- AlicenseNot gradedqualityCmaintenanceMCP tools for managing your self-hosted Supabase instance. Combines Edge Function CRUD, migration management, log monitoring, and Studio MCP proxy into a single endpoint.1MIT
- AlicenseAqualityAmaintenancePortkey Admin API control-plane MCP server with Prisma AIRS interoperability guidance.178393 npm6MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.7 npmMIT
- FlicenseNot gradedqualityDmaintenanceA modular MCP server exposing tools for integrating with services like GitHub, Redash, Jenkins, Figma, Jira, Confluence, Teams, Datadog, PagerDuty, Slack, and Presto, enabling users to manage these platforms through natural language via an MCP client.-
- FlicenseNot gradedqualityCmaintenanceMCP server for Minisend payment APIs, enabling stablecoin-to-local-currency payouts and on-ramps across Kenya, Nigeria, Ghana, and Uganda. Exposes tools for off-ramp, on-ramp, checkout, wallets, and API knowledge, with permissions-based tool visibility.-
TDQS
Scored across 28 tools
Most tools target a distinct resource and action, but there are clusters that could confuse an agent: create_connect_session vs create_standard_connect_session, get_connection vs get_connection_context, and the four connection-convention helpers all have overlapping boundaries. The descriptions are precise enough to disambiguate with careful reading, but the set is not immediately self-evident.
Tool names consistently use snake_case with an imperative verb prefix like list_, get_, create_, update_, delete_, and refresh_. Minor deviations like check_environment, stage_proxy_request_body, and describe_connection_convention break the dominant verb-noun pattern slightly, but the overall style is predictable and readable.
With 28 tools, the server exceeds the 25-tool threshold that starts to feel too heavy. The broad Nango domain (environments, integrations, connections, Connect sessions, proxy, and conventions) partially justifies the count, but many helper and convention tools add surface area that could likely be consolidated.
Core lifecycle coverage is strong: integrations have full CRUD, connections support listing, reading, importing, deleting, and targeted updates, and Connect session creation is covered. Gaps include no environment create/update/delete and no generic connection update endpoint, but these are minor given the server's apparent scope.