Skip to main content
Glama

Related Servers

Alternatives to project-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      A FastMCP server that exposes REST API endpoints as Model Context Protocol tools for AI agents. It provides a template for wrapping upstream APIs and includes deployment support for Docker and OpenShift.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A FastMCP-based server that provides tools for API discovery and execution, hierarchical category management, and SQL query execution through the Model Context Protocol.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      FastMCP is a comprehensive MCP server allowing secure and standardized data and functionality exposure to LLM applications, offering resources, tools, and prompt management for efficient LLM interactions.
      3
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to create and deploy FastMCP servers with embedded MCP Apps for interactive tool-to-UI flows. It also provides production-ready authentication, licensing, usage reporting, and health-check endpoints.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A FastMCP server that scans Azure DevOps work items, flags overdue or stale items, emails assignees via Microsoft Graph, and provides tools to delve into stalled items, wiki pages, and write operations with safety gates.
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server built with FastMCP that enables dynamic tool loading and configuration from individual Python files. It provides a flexible framework for automatically discovering, testing, and running tools via Stdio or HTTP transport modes.
      1
      -

    TDQS

    B3.3/5.0

    Scored across 14 tools

    Disambiguation3/5

    Several tools overlap in purpose: run_command can duplicate run_tests and deploy, read_file/get_config both read config files, edit_file/update_config can both modify config, and list_artifacts/list_directory/search_files share discovery space. Descriptions help, but an agent could plausibly misselect among these.

    Naming Consistency4/5

    Most tools follow a readable snake_case verb_noun pattern (read_file, write_file, get_config, update_config, run_tests). Minor deviations include _substitute_vars with a leading underscore, plus deploy and status as bare verb/noun names.

    Tool Count5/5

    14 tools is within the typical well-scoped range and matches a project lifecycle surface spanning files, config, tests, deployment, commands, status, and logs. No excessive proliferation or obvious under-provisioning.

    Completeness4/5

    Core project operations are covered: file read/write/list/search/edit, config get/update, test running, deployment, command execution, status, and logs. Minor gaps remain around explicit delete_file/create_directory and artifact lifecycle beyond listing, though run_command can work around many of them.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues