Mcp Directory

Created By
Go-To-Seaa year ago
discover MCP Servers and Clients for Claude Integration
Overview

What is Mcp Directory?

Mcp Directory is a project designed to help users discover MCP Servers and Clients for Claude Integration.

How to use Mcp Directory?

To use Mcp Directory, clone the repository from GitHub, install the necessary dependencies, prepare the database, set environment variables, and run the development server to preview the site.

Key features of Mcp Directory?

  • Easy discovery of MCP Servers and Clients.
  • Quick start guide for setup and installation.
  • Community support through Telegram and Discord.

Use cases of Mcp Directory?

  1. Integrating Claude with various MCP Servers.
  2. Setting up a local development environment for MCP projects.
  3. Collaborating with the community for MCP-related queries.

FAQ from Mcp Directory?

  • What is the purpose of Mcp Directory?

Mcp Directory helps users find and integrate MCP Servers and Clients for Claude.

  • Is there community support available?

Yes! You can join the MCP Server Telegram and Discord for community support.

  • What technologies are used in Mcp Directory?

The project is built using TypeScript and requires a Supabase database.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Go-To-Sea
Star
2
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago