MCP-Server

Created By
datziia year ago
MCP Server for tool calling
Overview

what is MCP-Server?

MCP-Server is a server designed for tool calling, allowing users to interact with various tools through API endpoints.

how to use MCP-Server?

To use MCP-Server, create a virtual environment, install the necessary dependencies, and start the server using the provided commands.

key features of MCP-Server?

  • Provides API endpoints for checking server status and accessing available tools.
  • Easy setup with a virtual environment and dependency management.
  • Supports Python for server-side operations.

use cases of MCP-Server?

  1. Integrating various tools into applications via API calls.
  2. Monitoring the status of the server and tools.
  3. Facilitating automated workflows that require tool interactions.

FAQ from MCP-Server?

  • What programming language is MCP-Server built with?

MCP-Server is built using Python.

  • How do I check if the server is running?

You can check the server status by accessing the /v1/status/ endpoint.

  • Can I add more tools to the MCP-Server?

Yes! You can extend the server by adding more tools to the configuration.

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

2 days ago