MCP Demo App

Created By
sameerfaa year ago
A simple Node.js/Express API server using TypeScript for managing products and orders, with Model Context Protocol (MCP) integration.
Overview

What is MCP Demo App?

MCP Demo App is a simple Node.js/Express API server built with TypeScript, designed for managing products and orders, and integrating with the Model Context Protocol (MCP).

How to use MCP Demo App?

To use the MCP Demo App, clone the repository, install the dependencies, build the project, and run the API server. You will need to authenticate using a Bearer token for API access.

Key features of MCP Demo App?

  • RESTful API for managing products and orders
  • Bearer token authentication for secure access
  • Data stored in JSON files for easy management
  • MCP server tools for product and order queries
  • TypeScript for enhanced type safety and development experience

Use cases of MCP Demo App?

  1. Managing product inventories in an e-commerce application.
  2. Processing customer orders and tracking their status.
  3. Integrating with other services using the MCP server tools for data retrieval.

FAQ from MCP Demo App?

  • What technologies are used in MCP Demo App?

The app is built using Node.js, Express, and TypeScript.

  • How do I authenticate with the API?

You need to include a Bearer token in the Authorization header for all API requests except the health check endpoint.

  • Can I run this app in production?

Yes, after building the project, you can run it in production mode.

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