MCP clients
14 applications that can connect to an MCP server: code editors, desktop assistants, terminal agents, agent frameworks and workflow automation platforms. Each entry records where its configuration lives, which transports it speaks, which parts of the protocol it implements, and the date those details were last checked.
The transport column decides compatibility more than anything else. A client that cannot start a local process only works with servers publishing an HTTP or SSE endpoint, which rules out most packaged servers. Every client page carries ready to paste configuration for both cases where the client supports them.
Automation platforms are a special case
n8n, Zapier and Make run on their own infrastructure, so they cannot start a local stdio server. They only work with servers that publish an HTTP or SSE endpoint. Several of them also publish their own MCP server, which means they appear on both sides of the protocol: a client that calls other servers, and a server that other clients call.