MCP JS Server Template

Created By
ryakera year ago
Simplified MCP Server Template for Node.js
Overview

what is MCP JS Server Template?

MCP JS Server Template is a simplified template for creating Model Context Protocol (MCP) servers in JavaScript, designed for integration with Claude Desktop. It provides a basic structure for developing custom MCP servers with minimal boilerplate code.

how to use MCP JS Server Template?

To use the MCP JS Server Template, clone the repository, install the necessary dependencies, and configure it in your Claude Desktop configuration file. You can then run the server and utilize the provided tools.

key features of MCP JS Server Template?

  • Implements standard MCP server initialization
  • Provides two basic tools: about and hello
  • Follows MCP protocol version 2024-11-05
  • Uses @modelcontextprotocol/sdk for server implementation
  • Includes error handling and logging

use cases of MCP JS Server Template?

  1. Creating custom MCP servers for various applications.
  2. Integrating with Claude Desktop for enhanced functionality.
  3. Rapid prototyping of server implementations with minimal setup.

FAQ from MCP JS Server Template?

  • What are the prerequisites for using this template?

You need Node.js (v16 or later) and the @modelcontextprotocol/sdk npm package.

  • Can I extend this template for my own MCP server?

Yes! You can copy the template, modify the tools, and implement custom handlers.

  • Is there any support for advanced features?

This template is minimal and does not include advanced security features or extensive error handling.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ryaker
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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