MCP Config

Created By
marcusschiessera year ago
A CLI tool for easy installation of MCP servers and managing their configuration
Overview

What is MCP Config?

MCP Config is a command-line interface (CLI) tool designed for managing configurations of MCP servers for MCP clients, specifically tailored for Codeium Windsurf.

How to use MCP Config?

To use MCP Config, simply run npx mcp-config in your terminal. You can select an already installed MCP server and perform actions like configure, remove, or view details. To add a new MCP server, press the 'a' key and choose from the repository or run npx mcp-config <server-name> directly.

Key features of MCP Config?

  • Repository of MCP servers for easy access
  • One-line installation for MCP servers
  • Interactive prompts for configuring and adding servers
  • Ability to view and remove existing server configurations

Use cases of MCP Config?

  1. Managing multiple MCP server configurations efficiently.
  2. Simplifying the installation process of new MCP servers.
  3. Providing an interactive interface for server management tasks.

FAQ from MCP Config?

  • Is MCP Config easy to use?

Yes! It provides an interactive CLI that simplifies server management tasks.

  • Can I add new MCP servers easily?

Absolutely! You can add new servers with just a few keystrokes.

  • What programming language is MCP Config built with?

MCP Config is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
marcusschiesser
Star
37
Language
TypeScript
License
MIT license
Tags

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)

a day ago
Crevio

2 days ago