🛠️ Simple MCP Example with Claude and a Local JSON HTTP Server

Created By
sunmera year ago
Simple MCP server using Claude to interact with a local JSON server
Overview

What is the Simple MCP Example?

The Simple MCP Example is a project that demonstrates how to set up a local JSON HTTP server and interact with it using Claude, a MacOS desktop application, through the Model-Computer Protocol (MCP).

How to use the Simple MCP Example?

To use this project, you need to install Node.js and Claude for MacOS. After setting up the project, you can run the mock API and MCP server, and then interact with the server using Claude by sending commands.

Key features of the Simple MCP Example?

  • Integration with Claude for seamless interaction with a local JSON server.
  • Step-by-step setup guide for easy installation and configuration.
  • Ability to send commands to the server and receive responses directly in Claude.

Use cases of the Simple MCP Example?

  1. Testing local JSON APIs with Claude.
  2. Learning how to set up and configure a local server using Node.js.
  3. Experimenting with the Model-Computer Protocol for various applications.

FAQ from the Simple MCP Example?

  • What are the prerequisites for this project?

You need Node.js and Claude for MacOS installed, along with a basic understanding of local servers.

  • How do I run the project?

Install the dependencies, configure the MCP server in Claude, and run the mock API and MCP server.

  • Can I use this project for production?

This project is primarily for educational and testing purposes, not recommended for production use.

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

Recommend Servers

View All
Voyei

2 hours 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