custom-mcp-servers

Created By
Dyno-Community-Code-Spacea year ago
Learn the ins and outs of Model Context Protocol, MCP servers, and custom implementations
Overview

what is custom-mcp-servers?

custom-mcp-servers is a project that focuses on the Model Context Protocol (MCP) and its custom implementations, providing insights and guidance on how to effectively utilize MCP servers.

how to use custom-mcp-servers?

To use custom-mcp-servers, visit the GitHub repository at custom-mcp-servers to access documentation and resources related to MCP servers and their configurations.

key features of custom-mcp-servers?

  • Comprehensive guides on Model Context Protocol
  • Examples of custom MCP server implementations
  • Community support and contributions

use cases of custom-mcp-servers?

  1. Developing custom applications using MCP servers.
  2. Learning about the architecture and functionality of MCP.
  3. Collaborating with the community on MCP-related projects.

FAQ from custom-mcp-servers?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework for managing context in applications, allowing for more dynamic and responsive interactions.

  • Where can I find more information?

You can find more information and resources on the GitHub repository.

  • Is there community support available?

Yes! The project encourages community contributions and discussions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Dyno-Community-Code-Space
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)

a day ago
Crevio

2 days ago