python-mcp-server-generator
Skill7 starsChanged 4 months agoMITView on GitHub
Generate a complete MCP server project in Python with tools, resources, and proper configuration
5 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- github/awesome-copilottheir own version, first seen Oct 25, 2026
- 0xrizz/os-manageredited, first seen Aug 28, 2026
- Adhamxon/claude-code-skillsword for word, first seen Jul 30, 2026
- ReaperOAK/ForgeOSword for word, first seen Jun 8, 2026
- tae0y/python-project-templateedited, first seen Mar 7, 2026
Other versions5 projects use a version of this.
Word for word · 2
- Adhamxon/claude-code-skills★ 2100% same
- ReaperOAK/ForgeOS★ 0100% same
Edited · 2
- tae0y/python-project-template★ 1495% same
- 0xrizz/os-manager★ 198% same
Wrote their own version · 1
- github/awesome-copilot★ 41ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-code-projectSkill
- goal-creatorSkill
- python-anti-patternsSkill
- python-background-jobsSkill
- python-design-patternsSkill
- python-error-handlingSkill
- python-performance-optimizationSkill
- pocmap-agentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 13 are common, 0 are distinctive, and 9 are very specific to this project.
13
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
Create a complete Model Context Protocol (MCP) server in Python with the following specifications:
- Common: line 12
Project Structure: Create a new Python project with proper structure using uv
- Common: line 15
Tools: Create at least one useful tool with proper type hints
- Very specific: line 22
Add MCP SDK: uv add "mcp[cli]"
- Very specific: line 23
Create main server file (e.g., server.py)
- Very specific: line 24
Add .gitignore for Python projects
- Very specific: line 28
Use FastMCP class from mcp.server.fastmcp
- Very specific: line 34
Use @mcp.tool() decorator on functions
- Common: line 35
Always include type hints - they generate schemas automatically
- Common: line 36
Write clear docstrings - they become tool descriptions
- Common: line 37
Use Pydantic models or TypedDicts for structured outputs
- Very specific: line 42
Add resources with @mcp.resource() decorator
- Very specific: line 43
Use URI templates for dynamic resources: "resource://{param}"
- Very specific: line 44
Add prompts with @mcp.prompt() decorator
- Common: line 48
Use type hints for all function parameters and returns
- Common: line 49
Write docstrings for tools, resources, and prompts
- Common: line 50
Follow PEP 8 style guidelines
- Common: line 51
Use async/await for asynchronous operations
- Common: line 53
Add inline comments for complex logic
- Very specific: line 81
Test with MCP Inspector: uv run mcp dev server.py
- Common: line 97
Use type hints everywhere - they're not optional
- Common: line 103
Test tools independently before LLM integration
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Generate Python MCP Server
Create a complete Model Context Protocol (MCP) server in Python with the following specifications:
Requirements
- Project Structure: Create a new Python project with proper structure using uv
- Dependencies: Include mcp[cli] package with uv
- Transport Type: Choose between stdio (for local) or streamable-http (for remote)
- Tools: Create at least one useful tool with proper type hints
- Error Handling: Include comprehensive error handling and validation
Implementation Details
Project Setup
- Initialize with
uv init project-name - Add MCP SDK:
uv add "mcp[cli]" - Create main server file (e.g.,
server.py) - Add
.gitignorefor Python projects - Configure for direct execution with
if __name__ == "__main__"
Server Configuration
- Use
FastMCPclass frommcp.server.fastmcp - Set server name and optional instructions
- Choose transport: stdio (default) or streamable-http
- For HTTP: optionally configure host, port, and stateless mode
Tool Implementation
- Use
@mcp.tool()decorator on functions - Always include type hints - they generate schemas automatically
- Write clear docstrings - they become tool descriptions
- Use Pydantic models or TypedDicts for structured outputs
- Support async operations for I/O-bound tasks
- Include proper error handling
Resource/Prompt Setup (Optional)
- Add resources with
@mcp.resource()decorator - Use URI templates for dynamic resources:
"resource://{param}" - Add prompts with
@mcp.prompt()decorator - Return strings or Message lists from prompts
Code Quality
- Use type hints for all function parameters and returns
- Write docstrings for tools, resources, and prompts
- Follow PEP 8 style guidelines
- Use async/await for asynchronous operations
- Implement context managers for resource cleanup
- Add inline comments for complex logic
Example Tool Types to Consider
- Data processing and transformation
- File system operations (read, analyze, search)
- External API integrations
- Database queries
- Text analysis or generation (with sampling)
- System information retrieval
- Math or scientific calculations
Configuration Options
- For stdio Servers:
- Simple direct execution
- Test with
uv run mcp dev server.py - Install to Claude:
uv run mcp install server.py
- For HTTP Servers:
- Port configuration via environment variables
- Stateless mode for scalability:
stateless_http=True - JSON response mode:
json_response=True - CORS configuration for browser clients
- Mounting to existing ASGI servers (Starlette/FastAPI)
Testing Guidance
- Explain how to run the server:
- stdio:
python server.pyoruv run server.py - HTTP:
python server.pythen connect tohttp://localhost:PORT/mcp
- stdio:
- Test with MCP Inspector:
uv run mcp dev server.py - Install to Claude Desktop:
uv run mcp install server.py - Include example tool invocations
- Add troubleshooting tips
Additional Features to Consider
- Context usage for logging, progress, and notifications
- LLM sampling for AI-powered tools
- User input elicitation for interactive workflows
- Lifespan management for shared resources (databases, connections)
- Structured output with Pydantic models
- Icons for UI display
- Image handling with Image class
- Completion support for better UX
Best Practices
- Use type hints everywhere - they're not optional
- Return structured data when possible
- Log to stderr (or use Context logging) to avoid stdout pollution
- Clean up resources properly
- Validate inputs early
- Provide clear error messages
- Test tools independently before LLM integration
Generate a complete, production-ready MCP server with type safety, proper error handling, and comprehensive documentation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

