Skip to main content
Glama
Edison-Watch

mcp-template

by Edison-Watch

Related Servers

Alternatives to mcp-template

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Python template for building MCP servers with enterprise features including registry integration, configuration management, structured logging, and extensible patterns for tools, resources, and prompts.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A production-grade, extensible Python template for building Model Context Protocol servers with support for Streamable HTTP and stdio transports. It provides a structured framework for implementing tools, resources, and prompts with built-in authentication, observability, and background task management.
      11
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A foundational template for building MCP servers in Python using Streamable HTTP transport. Provides example implementations of tools, resources, and prompts to help developers create custom MCP integrations for AI assistants.
      -
    • F
      license
      A
      quality
      C
      maintenance
      Serves as a reusable Python FastMCP template that lets developers quickly scaffold and extend MCP servers with tools, resources, prompts, services, and schemas over stdio or HTTP.
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      A Python MCP server template with environment-driven configuration, key authentication with rotation, JSON logging, and a golden-set eval harness for building production-ready MCP servers.
      2
      MIT

    TDQS

    C2.5/5.0

    Scored across 50 tools

    Disambiguation1/5

    Many tools are near-duplicates with different names: gmail_archive_thread and gmail_inbox.archive, gmail_mark_thread_done and gmail_inbox.mark_done, gmail_composer.send and gmail_send, settings.subscribe and webhook_subscribe. An agent cannot reliably tell which variant is appropriate for a given request.

    Naming Consistency1/5

    Naming is a mix of dot-separated app namespaces (gmail_inbox.set_focus, gmail_composer.save_draft), flat snake_case names (gmail_archive_thread, webhook_subscribe), and inconsistent verb orders. The same operation appears as both gmail_mark_thread_done and gmail_inbox.mark_done, so there is no predictable pattern.

    Tool Count1/5

    At 50 tools, the surface is far too large for the apparent Gmail-plus-webhooks scope. Many tools are aliases for the same underlying actions split across UI and headless variants, and the set could likely be reduced by more than half.

    Completeness4/5

    The underlying workflows are well covered: Gmail connection, inbox reading and triage, draft compose/send/discard, attachments, reply/forward, archive/done/read, watch, a curation ledger, and webhook settings. Minor gaps like permanent trash or expanded label management exist but are not severe.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive