MCP Demo

Created By
tanjibpaa year ago
Overview

What is MCP Demo?

MCP Demo is a demonstration implementation of a Model Context Protocol (MCP) server designed to manage organizations and devices, calculate distances between devices and their associated organizations, and provide tools for data interaction.

How to use MCP Demo?

To use MCP Demo, clone the repository, set up a virtual environment, configure the database connection in a .env file, and run the server using the provided commands.

Key features of MCP Demo?

  • Database Integration: Connects to a PostgreSQL database for managing organizations and devices.
  • Distance Calculation: Utilizes the Haversine formula for calculating distances between devices and organizations.
  • MCP Tools: Offers tools to fetch organizations, devices, and calculate distances.

Use cases of MCP Demo?

  1. Managing organizational data and device information.
  2. Calculating geographical distances for logistics and planning.
  3. Providing a backend service for applications requiring device management.

FAQ from MCP Demo?

  • What technologies are used in MCP Demo?

MCP Demo is built using Python and integrates with PostgreSQL for database management.

  • How can I set up the database?

You can set up the database by running the SQL script provided in the repository after configuring your environment variables.

  • Is there any support for additional features?

Yes, the MCP framework allows for extensibility, and additional features can be implemented as needed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tanjibpa
Star
0
Language
Python
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