Useful Model Context Protocol Servers (MCPS)

Created By
daltonnyxa year ago
A collection of standalone Python scripts that implement Model Context Protocol (MCP) servers for various utility functions. Each server provides specialized tools that can be used by AI assistants or other applications that support the MCP protocol.
Overview

What is Useful Model Context Protocol Servers (MCPS)?

Useful Model Context Protocol Servers (MCPS) is a collection of standalone Python scripts that implement Model Context Protocol (MCP) servers for various utility functions, enabling AI assistants to extend their capabilities by calling specialized functions.

How to use Useful MCPS?

To use Useful MCPS, clone the repository from GitHub, install the required dependencies, and run the desired MCP server using the uv command with the appropriate directory and script name.

Key features of Useful MCPS?

  • Standalone Python scripts for various utility functions.
  • Supports multiple MCP servers for different tasks (e.g., YouTube data extraction, Word document processing, PlantUML rendering, Mermaid chart rendering).
  • Easy integration with AI assistants and applications that support the MCP protocol.

Use cases of Useful MCPS?

  1. Extracting chapters and subtitles from YouTube videos.
  2. Processing Word document templates and converting them to PDF.
  3. Rendering diagrams using PlantUML and Mermaid.

FAQ from Useful MCPS?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized way for AI assistants to interact with external tools and services, allowing them to call specialized functions provided by MCP servers.

  • How do I install Useful MCPS?

Clone the repository and install the uv package using pip. Dependencies are managed per-MCP via pyproject.toml.

  • Can I add new MCP servers?

Yes! You can create a new directory for your MCP, define its metadata and dependencies, and implement the required logic.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
daltonnyx
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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