Project directory

MCP

Servers, registries and updates to the Model Context Protocol.

Playwright MCP

Playwright MCP

Playwright MCP gives MCP clients browser automation tools based on structured accessibility snapshots.

  • Page model. Accessibility snapshots expose page structure for interactions without requiring a vision model. Source ↗
  • Runtime. The npm package requires Node.js 20 or newer. Clients can launch it locally or connect to a standalone HTTP server. Source ↗

Publisher update ·

Playwright MCP v0.0.86 ↗

Scheduled · awaiting first completed check

Desktop Commander

Desktop Commander

Desktop Commander exposes file operations, interactive terminal sessions and process management through MCP.

  • Local delivery. The MIT-licensed server has a Node.js package and a Docker image. The Docker option does not require Node.js on the host. Source ↗
  • Remote delivery. A separate Remote MCP connection serves web clients through a launcher running on the user’s macOS, Linux or Windows machine. Source ↗

Scheduled · awaiting first completed check

MCP reference servers

MCP reference servers

The MCP reference servers demonstrate protocol features and SDK usage through a collection of example implementations.

  • Catalog. The maintained examples cover Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking, and Time. Source ↗
  • Distribution. The TypeScript packages run through npm and the Python packages through PyPI, using tools such as npx and uvx. Source ↗

Publisher update ·

MCP reference servers v2.5.0 ↗

Scheduled · awaiting first completed check

MCP Inspector

MCP Inspector

MCP Inspector is a local developer tool for examining and testing MCP servers.

  • Interfaces. One npm package provides a web UI, terminal UI, scriptable CLI, and experimental mcpdo client for reusing named connections. Source ↗
  • Runtime. The v2.16.0 package requires Node.js 22.23.4 or later in the 22 line, 24.22.1 or later in the 24 line, or at least 26.12.1. Source ↗

Publisher update ·

MCP Inspector 2.16.0 ↗

Scheduled · awaiting first completed check

Ruflo

Ruflo

Ruflo adds agent coordination and persistent memory tools to Claude Code and other MCP clients.

  • Local delivery. The MIT-licensed Ruflo package exposes a local npm MCP entry point that clients can run without initializing a project. Source ↗
  • Project setup. The full Claude Code integration installs project hooks, agent definitions, memory and the MCP server. Source ↗

Publisher update ·

Ruflo 3.77.2 tightens managed-session ownership ↗

Scheduled · awaiting first completed check

Supabase MCP

Supabase MCP

Supabase MCP exposes Supabase project operations and documentation to MCP clients.

  • Hosted access. The hosted HTTP endpoint prompts for Supabase sign-in and organization selection. Source ↗
  • Project scope. A project reference disables account-level tools, and read-only mode runs queries as a read-only Postgres user. Source ↗

Publisher update ·

Supabase MCP Server v0.18.0 ↗

Scheduled · awaiting first completed check

Context7

Context7

Context7 supplies coding agents with library documentation and code examples matched to the requested library version.

  • Lookup model. The MCP tools resolve a library name to an index ID and query documentation by that ID. A language hint ranks matching code examples first. Source ↗
  • Delivery. Context7 provides a hosted MCP endpoint and a local npm server package. Its separate ctx7 CLI and skills can retrieve documentation without MCP. Source ↗

Publisher update ·

Context7 MCP 4.7.3 ↗

Scheduled · awaiting first completed check

agent-device

agent-device

agent-device gives coding agents shared CLI and MCP tools for inspecting, controlling and verifying apps.

  • MCP delivery. The MIT-licensed package starts a local stdio server that uses the same execution runtime as the CLI. Source ↗
  • Runtime. The CLI requires Node.js 22.12 or newer. Web automation requires Node.js 24 or newer. Source ↗

Publisher update ·

agent-device 0.21.38 revises its MCP tool surface ↗

Scheduled · awaiting first completed check

REA

REA

REA exposes local software inspection workflows through an MCP server and a CLI.

  • Access. The MIT-licensed rea-agents npm package runs locally. Setup registers the MCP server and matching workflow instructions with supported clients, including Codex and Claude Code. Source ↗
  • Static inventory. Built-in readers report compiler and module metadata in Go binaries and embedded crate metadata in Rust binaries built with cargo-auditable. Source ↗

Publisher update ·

REA 6.9.0 adds offline V8 code-cache inspection ↗

Scheduled · awaiting first completed check

Firecrawl MCP

Firecrawl MCP

Firecrawl MCP exposes web search, page scraping, site crawling and document parsing to MCP clients.

  • Keyless scope. The hosted Streamable HTTP endpoint offers rate-limited search, scrape and parse without an account credential. Source ↗
  • Cloud access. OAuth and API-key sessions can expose additional tools, subject to plan and team policy. The credit usage tool reports remaining team credits and historical use. Source ↗

Publisher update ·

Firecrawl MCP v3 service update ↗

Scheduled · awaiting first completed check

Chrome DevTools MCP

Chrome DevTools MCP

Chrome DevTools MCP connects coding clients to a live Chrome browser for debugging, automation and performance analysis.

  • Diagnostics. DevTools records performance traces and extracts insights. The server exposes network requests and console messages with source-mapped stacks. Source ↗
  • Runtime. The local npm server uses a Node.js LTS release. Google Chrome and Chrome for Testing are the officially supported browsers. Source ↗

Publisher update ·

Chrome DevTools MCP v1.13.0 ↗

Scheduled · awaiting first completed check

MCP Registry

MCP Registry

MCP Registry indexes publisher-supplied metadata for discovering public MCP servers.

  • Public API. The hosted v0.1 servers endpoint exposes paginated listings without an account token. Source ↗
  • Artifact scope. The registry stores metadata and links to artifacts distributed elsewhere, such as npm, PyPI, or container registries. Source ↗

Publisher update ·

MCP Registry v1.8.9 ↗

Scheduled · awaiting first completed check

Scrapling MCP server

Scrapling MCP server

The Scrapling MCP server exposes web page fetching and targeted content extraction from the Scrapling Python package.

  • Package. The self-hosted server comes from the BSD-3-Clause Scrapling package through its optional scrapling[ai] extra. Source ↗
  • Extraction. One-shot tools fetch a URL directly over HTTP or render JavaScript in a browser. CSS selectors can narrow the returned content. Source ↗

Publisher update ·

Scrapling 0.5.1 adds motion capture to MCP ↗

Scheduled · awaiting first completed check

Tavily MCP

Tavily MCP

Tavily MCP exposes Tavily’s web search, extraction, site mapping, crawling and hosted research tools to agents.

  • Keyless scope. A dedicated request header enables free, rate-limited search and extraction on the hosted server without an account. Source ↗
  • Authenticated access. The hosted server supports OAuth or an API key, with mapping, crawling and research among the additional tools. Source ↗

Publisher update ·

Tavily MCP 0.2.22 ↗

Scheduled · awaiting first completed check

Exa MCP

Exa MCP

Exa MCP gives agent clients web search, page retrieval and access to Exa’s multi-step research service.

  • Hosted access. Keyless connections provide rate-limited search and fetch. OAuth or an API key applies the Exa team’s plan and limits and enables authenticated Exa Agent calls. Source ↗
  • Local runtime. The exa-mcp-server npm package can run locally with an Exa API key. Source ↗

Publisher update ·

Exa Agent and Exa Connect in MCP ↗

Scheduled · awaiting first completed check

Figma Context MCP

Figma Context MCP

Framelink MCP for Figma turns Figma file and node data into layout and style context for coding agents.

  • Package. This community implementation ships as the MIT-licensed figma-developer-mcp npm package and requires Node.js 20.20.0 or newer. Source ↗
  • API limits. Figma REST API limits vary by endpoint tier, seat type, and the plan where the file is hosted. Source ↗

Publisher update ·

Framelink MCP for Figma v0.13.2 ↗

Scheduled · awaiting first completed check

Notion MCP Server

Notion MCP Server

Notion has ended active support for this self-hosted MCP server. Its hosted Notion MCP service is a separate product.

  • Support status. Notion has ended active support for this repository and maintains the separate OAuth-based Remote Notion MCP service. Source ↗
  • Access. An internal Notion integration token supplies permissions, and the integration can only reach content connected to it. Source ↗

Publisher update ·

Notion MCP Server v2.1.0 ↗

Scheduled · awaiting first completed check

GitHub MCP Server exposes GitHub repository, issue, pull request and Actions operations to MCP clients.

  • Hosted access. GitHub hosts a remote endpoint that accepts OAuth from supported clients or a GitHub personal access token. Organization policies can govern access. Source ↗
  • Local access. The MIT-licensed local server can run from a container image or a Go build. It uses GitHub credentials for API access. Source ↗

Monitored