🤖 Model Context Protocol (MCP) Examples

Created By
sur950a year ago
Overview

What is Model Context Protocol (MCP) Examples?

Model Context Protocol (MCP) Examples is a repository containing modular MCP agent servers built using the Model Context Protocol TypeScript SDK. Each subdirectory in src/ is a self-contained MCP server with various tools and prompts for tasks like code analysis and summarization.

How to use MCP Examples?

To use MCP Examples, clone the repository, install the dependencies, and start the MCP server. You can also set up a local .env file for configuration. The server will run at http://localhost:3000/mcp.

Key features of MCP Examples?

  • Modular design with self-contained MCP servers
  • Tools for code analysis and summarization
  • Easy setup and local testing with MCP Inspector

Use cases of MCP Examples?

  1. Analyzing local code repositories for structure and content.
  2. Summarizing code documentation.
  3. Debugging and testing MCP-based servers using MCP Inspector.

FAQ from MCP Examples?

  • What is the purpose of the MCP Inspector?

MCP Inspector is a UI debugger for MCP-based servers that allows for manual testing and debugging.

  • How do I start the MCP server?

You can start the MCP server by running npm run dev after installing the dependencies.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sur950
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