mcp-server-template
Provides a tool to fetch Python package project information from PyPI, such as package metadata and release details, while safely excluding user-controlled content like project summaries.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-template get info on the requests package"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-template
Opinionated template for building read-only MCP servers that coding agents can actually use well: I/O seams with timeouts, offline tests, compact text outputs, least-privilege docs.
Start here → BUILDING.md — the full workflow from idea to published server (~half a day).
What's inside: a working example server (pypi_project fixed-origin HTTP tool behind a stubbed seam + word_stats pure tool), offline test suite, CI workflow, CLAUDE.md conventions, and a README skeleton below.
The network example deliberately does not accept arbitrary URLs. "Read-only" does not make a URL fetcher safe: unrestricted destinations and followed redirects can expose loopback, private-network, or cloud-metadata services. pypi_project constructs only https://pypi.org/... requests, rejects URL/path-shaped input, never follows redirects, caps the decoded response at 2 MiB, and applies a 15-second whole-operation deadline.
README skeleton for your server (replace this whole file)
# mcp-<name>+ one-line value prop in bold4-line usage transcript (You: … / Agent: → tool calls / Agent: answer)
Tools table (tool → what it returns)
Install:
claude mcp add <name> -- python -m mcp_<name>with any token preloaded into the launching environment from your shell or OS secret manager — never a-e TOKEN=...literal (command arguments can enter shell history and process listings) — plus a.mcp.jsonblock using an env reference ("env": { "TOKEN": "${TOKEN}" })Token scope / security (least privilege, read-only statement)
Design notes (why read-only, why compact text, why timeouts)
License + contact line
Use the structure above directly; replace every template name and example before publishing a derived server.
Related MCP server: Kroki MCP
Security and privacy
The example sends only the supplied package name to PyPI. Do not put secrets or private identifiers in tool arguments.
PyPI project summaries are uploader-controlled prose, so the example deliberately omits them from agent-visible output. Treat all external text as untrusted data.
Never log credentials, authorization headers, raw private responses, or user prompts.
Document which external service receives each argument. Private CI logs and internal URLs are sensitive even when a tool only reads them.
Keep arbitrary URL fetching out of derived servers unless you implement a destination allowlist and a transport that cannot be bypassed by redirects or DNS rebinding.
Development
python -m pip install -e ".[dev]"
ruff check . && ruff format --check .
pytest
python -m buildMIT — see LICENSE.
Available Tools
2 toolspypi_projectA
Look up one PyPI project: returns its current version, Python requirement, and request latency. Use before checking a Python dependency's compatibility. Only the fixed https://pypi.org API is contacted; URLs are rejected. Uploader prose such as the project summary is deliberately omitted.
Inputs: project (required). Returns: result
word_statsB
Word count plus the most frequent words of a text. Example of a pure, no-I/O tool: instant, deterministic, safe.
Inputs: text (required), top. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools target completely different domains (PyPI project lookup vs. text word statistics) with no overlap in function or purpose. An agent can easily select the correct tool without confusion.
Both tool names use consistent snake_case noun phrases (pypi_project, word_stats), adhering to a predictable naming pattern. Although not verb_noun, the convention is applied uniformly across the set.
Two tools is very thin for a functional MCP server and falls into the borderline '1-2 tools feels thin' category. However, as a template server, the small count may be intentional to demonstrate different tool types.
There is no coherent domain or lifecycle; the tools are isolated utilities with no way to list, search, update, or otherwise extend the surface. This leaves significant gaps for any real workflow an agent might attempt.
Related MCP Connectors
Primarily to be used as a template repository for developing MCP servers with FastMCP in Python, P…
Public read-only MCP server for Genvernium product and developer resources.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Related MCP Servers
- AlicenseAqualityNot gradedmaintenanceA production-ready TypeScript template for building MCP servers with dual transport support (stdio/HTTP), OAuth 2.1 foundations, SQLite caching, observability, and security features including PII sanitization and rate limiting.429 npm-
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server scaffold that features built-in authentication, Docker support, and a comprehensive CI/CD release pipeline. It provides a standardized template for deploying servers with multi-transport support and configurable read-only modes.MIT
- AlicenseNot gradedqualityDmaintenanceOpinionated template for building Node.js stdio and HTTP MCP servers.-
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server template with OAuth 2.1, RBAC, and audit logging for building secure, observable tool servers.MIT