MCP clients and servers
Choose a client, then find an MCP server for GitHub, browser, filesystem or Notion tasks.
Clients call tools; servers expose capabilities. These entries are checked against official documentation, not an end-to-end test of every client, account or mainland network.
MCP clients 4
Already have a client? Open its official connection guide, then choose a server below.
An AI coding agent that works across terminals, IDEs, and the web.
Listing checked: · 30+ days; recheck due
Official MCP docs ↗
Docs checked:OpenAI's AI coding agent for desktop, terminal, IDE, and cloud development tasks.
Listing checked:
Official MCP docs ↗
Docs checked:A code editor with built-in AI collaboration and development workflows.
Choose a server by task
These links point to maintainer documentation. Client subscriptions and connected services may charge separately; a local server does not make the whole workflow offline.
GitHub MCP ↗
Official remote service / local server
Work with repositories, issues and pull requests. Requires a GitHub account, repository permissions and a supported authentication method.
Docs checked:
Playwright MCP ↗
Browser automation
Operate websites through structured browser snapshots. A runtime and browser are required; the target site's network and sign-in requirements still apply.
Docs checked:
Filesystem MCP ↗
Local files
Read and write files in allowed directories. Requires a local Node.js runtime. Limit access to task-specific folders; model and client networking depends on their configuration.
Docs checked:
Notion MCP ↗
Notion workspace
Search, create and edit workspace content. Connect a Notion account and review the pages and workspace permissions granted to the client.
Docs checked:
