MCP System Backend

Created By
Avinashsharma01a year ago
Overview

What is MCP System Backend?

The MCP System Backend is a robust backend system designed for the Material Collection Point (MCP) System, which manages partners, pickups, orders, and wallet transactions.

How to use MCP System Backend?

To use the MCP System Backend, set up the environment by installing dependencies, configuring environment variables, and running the development server. You can then interact with the RESTful API endpoints for various functionalities.

Key features of MCP System Backend?

  • RESTful API for partner management, pickup scheduling, order processing, and wallet transactions.
  • Built with Node.js, Express, and MongoDB.
  • Role-based access control for different user types (e.g., MCP partners).

Use cases of MCP System Backend?

  1. Managing partner registrations and details.
  2. Scheduling and managing pickups for recyclable materials.
  3. Processing orders and managing wallet transactions for users and partners.

FAQ from MCP System Backend?

  • What technologies are used in MCP System Backend?

The backend is built using Node.js, Express, and MongoDB.

  • How do I set up the MCP System Backend?

Follow the setup instructions in the documentation, including installing dependencies and configuring environment variables.

  • Is there support for different user roles?

Yes, the system supports role-based access for users and partners.

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