Skip to main content
Glama
junna-legal

mcp-starter-kit

by junna-legal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-starter-kit

No user-submitted related servers found.

    Related Servers

    • mcp-server-toolkit

      sarmakska
      A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server starter with authentication, observability, and a plugin system for building and deploying MCP servers quickly.
      MIT

    • Model Context Protocol

      shubhamauti9
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server template that connects LLMs and AI agents to external data, tools, and services with built-in OAuth 2.1 authentication, Redis-backed session management, and a modular tools engine.
      1
      MIT

    • MCP Enterprise Tool Gateway

      BhavikMoradiya
      A
      license
      Not graded
      quality
      C
      maintenance
      An enterprise MCP server scaffold that provides secure, governed access to internal tools through RBAC, audit logging, rate limiting, and prompt-injection boundaries, with a FastAPI control plane and OpenTelemetry observability.
      MIT

    • Production-Ready FastMCP

      omy8573091
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-grade MCP server and client implementation with comprehensive features including structured logging, health checks, metrics, authentication, and RAG capabilities with PostgreSQL vector search. Supports both stdio and SSE transports with containerization and security features for enterprise deployment.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear boundaries between file, database, cache, semantic, webhook, and task operations. The only minor overlap is task_status handling both get and update, but the description clearly separates these behaviors, so no two tools appear to do the same thing.

    Naming Consistency2/5

    Naming conventions are mixed: some tools use hyphens (database-query, api-connector), others use underscores (file_read, task_status), and one is a single word (cache). The word order is also inconsistent, with most tools using noun_verb (file_read) but api-connector using a noun-noun pattern, and no uniform separator across the set.

    Tool Count4/5

    With 15 tools, the server sits at the upper boundary of a reasonable scope for a starter kit. Each tool covers a distinct capability, but the sheer variety (files, database, cache, semantic search, webhooks, tasks) makes it feel slightly broad, yet still justifiable for its purpose.

    Completeness3/5

    The tool surface covers core operations for each domain, but there are notable gaps: no file_delete or file_rename, no webhook_unregister, and no task_cancel or task_delete. These are common lifecycle operations that agents would likely need, making the set somewhat incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources