connectif-mcp
Related Servers
Alternatives to connectif-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceModel Context Protocol server for MCPGRAM that enables MCP clients to interact with connectors like GitHub, Slack, and Notion through stdio or Streamable HTTP transports.-

@hyperstar/mcpofficial
AlicenseNot gradedqualityBmaintenanceLocal stdio MCP server for Hyperstar headless workflows, providing tools for creator search, campaign management, bulk email, and inbox operations.238 npm-- AlicenseNot gradedqualityCmaintenanceActs as a stdio-to-HTTP proxy for the 1C runtime-MCP service, enabling MCP clients like Claude Desktop to interact with 1C tools.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes HubSpot CRM operations as tools over stdio, enabling any MCP client to query and modify HubSpot data.480 npmMIT
- FlicenseAqualityCmaintenanceUnofficial MCP server that exposes the PrijsProfeet API as validated tools for product search, price history, forecasts, deals, and matching. It can run via stdio or as an authenticated Streamable HTTP server.24-
- FlicenseBqualityBmaintenanceLocal MCP server for essential ClickUp workflows over stdio, exposing a bounded set of tools for search, task management, comments, tags, and workspace hierarchy.32-
TDQS
Scored across 12 tools
Each tool is clearly scoped to a distinct Connectif resource (contacts, purchases, products, etc.), so there is no overlap in target entities. An agent can easily choose the correct tool based on the resource name.
All tools follow the exact same pattern of `connectif_<resource>`, with consistent lowercase and underscore separation. This makes the naming perfectly predictable and easy to navigate.
The 12 tools cover the primary Connectif resource types (contacts, purchases, products, workflows, etc.) without being excessive. This falls comfortably within the well-scoped range for a domain-specific server.
The tool set covers core resources like contacts, purchases, products, and workflows, but the generic nature of each tool (requiring an 'action' parameter) obscures detailed operations. Some potentially important resources like campaigns or segments are missing, but the main lifecycle is represented.