my-mcp-server

Created By
zaruousa year ago
Overview

what is my-mcp-server?

my-mcp-server is a Model Context Protocol (MCP) server built with the mcp-framework, designed to facilitate the development and integration of various tools within a server environment.

how to use my-mcp-server?

To use my-mcp-server, install the dependencies using npm install, build the project with npm run build, and configure it with your Claude Desktop client.

key features of my-mcp-server?

  • Easy tool integration using CLI commands.
  • Example tool provided for quick start.
  • Supports local development and publishing to npm.

use cases of my-mcp-server?

  1. Developing custom tools for data processing.
  2. Integrating API clients for server communication.
  3. Creating file handlers for managing file operations.

FAQ from my-mcp-server?

  • How do I add a new tool?

Use the command mcp add tool <tool-name> to create a new tool.

  • Can I publish my tools?

Yes! After development, you can publish your tools to npm for others to use.

  • What is the project structure?

The project structure includes a src directory for source files, a package.json for project metadata, and a tsconfig.json for TypeScript configuration.

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