mcp-server and plane-mcp-server
These two Model Context Protocol (MCP) servers are competitors, as both aim to provide an MCP implementation for different platforms—Keboola and Plane, respectively—meaning users would choose one based on their underlying platform.
About mcp-server
keboola/mcp-server
Model Context Protocol (MCP) Server for the Keboola Platform
Exposes Keboola's data pipelines, transformations, and job orchestration as composable tools via the Model Context Protocol, enabling AI agents to query tables, create SQL transformations, trigger jobs, and manage development branches through a unified interface. Supports both a hosted remote server with OAuth authentication (for Cursor, Claude, Windsurf, and other MCP clients) and local deployment with configurable tool authorization via HTTP headers for access control. Built on Streamable HTTP transport with granular read-only and tool-filtering capabilities to safely integrate Keboola workflows into AI agent workflows.
About plane-mcp-server
makeplane/plane-mcp-server
Plane's Official Model Context Protocol Server 🔌 ⌨️ 🔥
Implements MCP for Plane's project management API with multiple transport options (stdio, HTTP, SSE) and flexible authentication via API keys, PAT tokens, or OAuth. Exposes 50+ tools covering projects, work items, cycles, modules, initiatives, and intake workflows—all validated against Plane's Pydantic SDK models. Designed for AI agent integration, supporting both local stdio connections and remote hosted deployments at mcp.plane.so.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work