agentleFS
zebbernzebbern/pocmap/.agents/skills/python-mcp-server-generator/SKILL.md

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

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
  1. Common:

    Create a complete Model Context Protocol (MCP) server in Python with the following specifications:

    line 8
  2. Common:

    Project Structure: Create a new Python project with proper structure using uv

    line 12
  3. Common:

    Tools: Create at least one useful tool with proper type hints

    line 15
  4. Very specific:

    Add MCP SDK: uv add "mcp[cli]"

    line 22
  5. Very specific:

    Create main server file (e.g., server.py)

    line 23
  6. Very specific:

    Add .gitignore for Python projects

    line 24
  7. Very specific:

    Use FastMCP class from mcp.server.fastmcp

    line 28
  8. Very specific:

    Use @mcp.tool() decorator on functions

    line 34
  9. Common:

    Always include type hints - they generate schemas automatically

    line 35
  10. Common:

    Write clear docstrings - they become tool descriptions

    line 36
  11. Common:

    Use Pydantic models or TypedDicts for structured outputs

    line 37
  12. Very specific:

    Add resources with @mcp.resource() decorator

    line 42
  13. Very specific:

    Use URI templates for dynamic resources: "resource://{param}"

    line 43
  14. Very specific:

    Add prompts with @mcp.prompt() decorator

    line 44
  15. Common:

    Use type hints for all function parameters and returns

    line 48
  16. Common:

    Write docstrings for tools, resources, and prompts

    line 49
  17. Common:

    Follow PEP 8 style guidelines

    line 50
  18. Common:

    Use async/await for asynchronous operations

    line 51
  19. Common:

    Add inline comments for complex logic

    line 53
  20. Very specific:

    Test with MCP Inspector: uv run mcp dev server.py

    line 81
  21. Common:

    Use type hints everywhere - they're not optional

    line 97
  22. Common:

    Test tools independently before LLM integration

    line 103

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generate Python MCP Server

Create a complete Model Context Protocol (MCP) server in Python with the following specifications:

Requirements

  1. Project Structure: Create a new Python project with proper structure using uv
  2. Dependencies: Include mcp[cli] package with uv
  3. Transport Type: Choose between stdio (for local) or streamable-http (for remote)
  4. Tools: Create at least one useful tool with proper type hints
  5. 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 .gitignore for Python projects
  • Configure for direct execution with if __name__ == "__main__"

Server Configuration

  • Use FastMCP class from mcp.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.py or uv run server.py
    • HTTP: python server.py then connect to http://localhost:PORT/mcp
  • 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.