Skip to main content
Glama
ramseychad1

sdlc-assist-mcp

by ramseychad1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to sdlc-assist-mcp

No user-submitted related servers found.

    Related Servers

    • Supabase MCP Server

      pipethedev
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to Supabase projects, enabling them to manage tables, query data, deploy Edge Functions, handle migrations, and access project resources through natural language commands.
      Apache 2.0

    • Supabase MCP Server

      bill143
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Supabase projects to AI assistants, enabling them to manage database tables, execute SQL queries, and deploy Edge Functions through natural language. It provides a comprehensive suite of tools for project administration, including logs access, documentation search, and environment configuration.
      Apache 2.0

    • PostgreSQL MCP Server

      melihbirim
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with PostgreSQL databases using natural language queries, providing secure read-only access to database schemas and SQL translation capabilities.
      6
      7 npm
      -

    • project-supabase-api

      andrewsetness
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely interact with Supabase through read-only and gated-write tools, with bounded queries, allowlists, and explicit project targeting.
      -
    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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: listing projects, getting a project summary, fetching a specific artifact, listing screens, getting tech preferences, and generating estimation. There is no overlap or ambiguity in their purposes.

    Naming Consistency5/5

    All tools follow the consistent pattern sdlc_<verb>_<noun> with lower_snake_case: sdlc_list_projects, sdlc_get_project_summary, sdlc_get_artifact, sdlc_get_screens, sdlc_get_tech_preferences, sdlc_generate_estimation. This is uniform and predictable.

    Tool Count5/5

    Six tools is an appropriate, well-scoped set for a read-and-estimate SDLC assist server. Each tool earns its place, and the count is within the ideal 3-15 range, making the server easy to navigate.

    Completeness4/5

    The tool surface covers the core read workflows: listing projects, retrieving any artifact, screen inventory, tech preferences, and generating estimates. Minor gaps exist, such as no tool to create or update projects/artifacts, but the stated purpose appears to be querying and estimation, so this is a reasonable limitation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources