MCP Quick Start Server

Created By
scriptstara year ago
MCP Server example for up and running in Node
Overview

What is MCP Quick Start Server?

MCP Quick Start Server is a simple example of a Model Context Protocol (MCP) server built with TypeScript, designed to demonstrate how to define basic tools, resources, and prompts for an AI client.

How to use MCP Quick Start Server?

To use the MCP Quick Start Server, clone the repository, install the dependencies, build the TypeScript code, and run the server using Node.js.

Key features of MCP Quick Start Server?

  • Tool: add: Adds two numbers and returns the sum.
  • Tool: fetch-chuck-jokes: Fetches a random Chuck Norris joke.
  • Resource: greeting: Provides personalized greetings based on a URI scheme.
  • Prompt: getGreetingAndJoke: Instructs an AI client to greet a user and tell a joke.

Use cases of MCP Quick Start Server?

  1. Building AI assistants that can perform arithmetic operations.
  2. Creating interactive applications that provide jokes and greetings.
  3. Developing tools that utilize the Model Context Protocol for various AI interactions.

FAQ from MCP Quick Start Server?

  • What is the Model Context Protocol?

It is a protocol designed for AI clients to interact with servers using defined tools and resources.

  • What are the prerequisites for running the server?

You need Node.js (v18.x or later) and npm installed on your machine.

  • How can I contribute to the project?

You can fork the repository, make changes, and submit a pull request.

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