mcp-node-server-template

Created By
SterlingChina year ago
Overview

what is mcp-node-server-template?

The mcp-node-server-template is a boilerplate template for creating Node.js server applications, designed to streamline the development process.

how to use mcp-node-server-template?

To use this template, clone the repository from GitHub, install the necessary dependencies using npm, and start the server with the provided command.

key features of mcp-node-server-template?

  • Pre-configured Node.js environment
  • Easy setup for RESTful APIs
  • Modular structure for scalability

use cases of mcp-node-server-template?

  1. Building RESTful APIs for web applications
  2. Creating microservices architecture
  3. Rapid prototyping of server-side applications

FAQ from mcp-node-server-template?

  • Is this template suitable for production use?

While it provides a solid foundation, further customization and security measures are recommended for production environments.

  • What technologies does this template use?

It primarily uses Node.js and Express.js for server-side development.

  • How can I contribute to this project?

Contributions are welcome! Please submit a pull request or open an issue on GitHub.

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