MCP Apps Directory
This directory is designed for teams that need practical Model Context Protocol tooling without wasting hours on unverified links, abandoned repositories, or unclear vendor claims. We keep the structure simple: what the app does, who maintains it, where official documentation lives, and which workflow category it supports. The goal is to help developers move from discovery to evaluation in minutes, not days.
Every listing is mapped to an original source so readers can audit the project page directly before installation. When available, we include maintainers, release signals, and product context that explain whether a tool is stable for production use or still in experimentation mode. This reduces the common risk of installing copied packages with similar names but different ownership.
Directory refresh
Use this page as the verification layer before a server install
The MCP ecosystem now has registry entries, MCP Apps, hosted servers, official browser automation servers, workflow servers, and fast-refresh community directories. This directory routes users toward source validation first, then deeper install pages only after the app or server looks trustworthy.
Source priority for MCP discovery
Fast directories are useful, but they are not the install authority. A production MCP shortlist should move from official registry or provider docs to freshness directories, then to community lists for long-tail discovery.
Official registry first
Use the official MCP Registry and upstream provider docs when the decision affects production installs, secrets, or compliance review.
Freshness directories second
Use PulseMCP and similar directories to spot fast-moving categories such as Playwright, Chrome DevTools, Memory, n8n, Postgres, GitHub, and Slack.
Community lists last
Use community catalogs for discovery, then verify package ownership, namespace, update date, and install command before copying anything into a client config.
Registry operations
Refresh like a directory, verify like a security checklist
MCP directories are changing quickly, and fast-updating competitors are useful trend sensors. This page now separates discovery freshness from installation trust so users can benefit from the pace without copying unverified commands.
Fast directory delta
Use fast-refresh competitors and community directories to spot new MCP categories, but do not treat their order as trust ranking.
Official source merge
When a listing has registry metadata, vendor docs, and GitHub source, show all three so teams can audit ownership quickly.
Install-command freshness
Exact npx searches should resolve to the newest supported package path, not a stale reference-server command copied from an old post.
Risk-routed next click
Send browser, filesystem, database, and network-capable servers to deeper safety pages before users paste commands into a client config.
Client and remote-server refresh
Sort MCP apps by where the risk enters the workflow
Current MCP directories are separating clients, remote servers, official servers, and scenario categories. This page now treats discovery as a routing job: choose the client layer, validate the server source, then open the scenario that matches the user's real task.
Client-first browsing
Many users now start with the client they already use, then ask which servers are safe to add. Keep client compatibility visible before install instructions.
Compare desktop extensionsRemote server split
Hosted and remote MCP servers need separate risk language because they introduce network, auth, and vendor availability checks.
Review security boundariesScenario routing
Directory pages should route users into concrete jobs such as scraping, database management, browser automation, and documentation.
Open scenario guideHow to evaluate an MCP app before using it
Start with a compatibility check: confirm your IDE or client actually supports the protocol features the app depends on. Next, review maintenance activity and issue responsiveness so you know whether critical bugs are likely to be fixed. Then inspect permissions, network behavior, and secret handling requirements. A useful app should be transparent about what data it reads, where requests are sent, and how credentials are stored.
If your organization has security review gates, treat this directory as a shortlist generator rather than an approval substitute. Pull candidate tools into your own validation pipeline, run sandbox tests, and verify that outbound domains, dependency trees, and update channels align with policy. This approach keeps discovery fast while preserving internal controls.
What makes this directory useful for AdSense quality
We publish original editorial guidance instead of thin link collections. Each category page explains decision criteria, risk boundaries, and operational tradeoffs for real teams. That means visitors get actionable context they can apply immediately, even if they do not click any single listing. The result is higher informational value, lower bounce risk, and stronger trust for both users and advertisers.
MCP Apps Directory
MCP Apps Directory: Clients, Reference Servers, and Verified Sources
Curated MCP apps and clients with clear source labels. Official sources are highlighted, community entries are separated, and the list is updated as the MCP ecosystem grows.
Official MCP Apps hosts
MCP Apps are currently supported by these hosts. This list comes from the official MCP Apps documentation and was refreshed on 2026-05-29; host support can still vary by extension capability.
MCP Registry status
The MCP Registry is the official metadata hub for servers. It is in preview, so listings can change as servers are validated and namespaces are verified.
Read the MCP Registry overviewFreshness signals added May 26
Browser automation, memory, workflow automation, and registry validation are now separate lanes
The fastest-moving MCP categories are not all the same job. Playwright and Chrome DevTools belong to browser execution, Memory and Filesystem belong to state and local context, n8n belongs to workflow orchestration, and the official Registry belongs to source validation. Use the filters below after choosing the lane.
Decision shortcuts
Route by the job you need the MCP layer to do
Claude Desktop App
Full MCP client support with local tools, resources, and prompts.
Claude Web
MCP Apps host for interactive UI resources rendered inside Claude conversations.
Claude Code
Code-focused Claude client with MCP support and roots.
Continue
Open-source AI code assistant with MCP resources and tools.
Sourcegraph Cody
Sourcegraph assistant that supports MCP resources via OpenCTX.
VS Code GitHub Copilot MCP
VS Code GitHub Copilot host support for MCP Apps and server-driven tools.
Zed
Editor with MCP prompt integration and tool workflows.
Firebase Genkit
GenAI SDK with MCP client support via the genkitx-mcp plugin.
MCPJam
MCP Apps-compatible host and testing surface for app-style MCP resources.
Playwright Browser Automation
Microsoft browser automation server for navigation, snapshots, interactions, and testing workflows.
Chrome DevTools MCP
Chrome DevTools team server for live Chrome inspection, performance traces, console checks, and automation.
n8n Instance MCP Server
n8n instance-level MCP access for enabled workflows, workflow management, testing, and data tables.
Neon MCP Server
Neon serverless Postgres MCP access for project, branch, and SQL workflows with source-first setup checks.
Everything
Reference server showcasing MCP prompts, resources, and tools.
Fetch
Reference server for web content fetching and conversion.
Filesystem
Reference server for secure file operations with access controls.
Git
Reference server for reading and manipulating Git repositories.
Memory
Reference server for knowledge graph-based persistent memory.
Submit updates
Have a client or server that should be listed? Share the details and we will verify the source before adding it.
Submit a listing