Claude MCP Configuration

Created By
carloslluberesa year ago
Working MCP server configurations for Claude - 16 servers functional
Overview

What is Claude MCP Configuration?

Claude MCP Configuration is a repository that provides working configurations for Claude MCP servers, ensuring that 16 servers are functional after extensive testing.

How to use Claude MCP Configuration?

To use this project, clone the repository from GitHub and refer to the configuration files and guides provided to set up your own MCP servers.

Key features of Claude MCP Configuration?

  • Detailed configuration for 16 working MCP servers.
  • Critical command type specifications for different server types.
  • Comprehensive guides and references for server commands.

Use cases of Claude MCP Configuration?

  1. Setting up and configuring Claude MCP servers for various applications.
  2. Troubleshooting and optimizing server configurations based on lessons learned.
  3. Reference for developers working with MCP server commands.

FAQ from Claude MCP Configuration?

  • What types of servers are included in this configuration?

The configuration includes NPX servers, UVX servers, and NODE servers.

  • Is there a guide for setting up the servers?

Yes, there is a detailed guide available in the repository.

  • What should I do if a server fails to start?

Refer to the lessons learned section in the guide for troubleshooting tips.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
carloslluberes
Star
0
Language
-
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)

4 hours ago
Gpt Scrambler

a day ago