Claude MCP (Master Control Program)

Created By
RLabs-Inca year ago
MCP server with different tools to extend Claude-code functionalities.
Overview

What is Claude MCP?

Claude MCP (Master Control Program) is a modular server-based tooling system designed to enhance Claude's code generation capabilities by providing access to the latest documentation and resources for various frameworks and libraries.

How to use Claude MCP?

To use Claude MCP, you can run it in either Personal Mode on your local machine or Shared Mode as a service for multiple users. Installation involves cloning the repository, installing dependencies, and running the server.

Key features of Claude MCP?

  • Modular architecture allowing for the addition of custom tools.
  • Documentation Fetcher tool that automatically detects the latest versions and scrapes documentation.
  • Integration with Claude Code CLI for seamless access to tools and documentation.
  • Support for various frameworks including LangChain, FastAPI, React, and more.

Use cases of Claude MCP?

  1. Enhancing code generation with up-to-date documentation.
  2. Facilitating team collaboration through shared server deployment.
  3. Custom tool development for specific documentation needs.

FAQ from Claude MCP?

  • Can Claude MCP be used for all programming languages?

Claude MCP primarily supports popular frameworks and libraries, but custom tools can be added for additional languages.

  • Is Claude MCP free to use?

Yes! Claude MCP is open-source and free to use.

  • How can I contribute to Claude MCP?

Contributions are welcome! You can submit a Pull Request on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RLabs-Inc
Star
0
Language
TypeScript
License
MIT 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)

a day ago
Crevio

2 days ago