Skip to main content
Glama
vinhgiga

obox-mcp

by vinhgiga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to obox-mcp

No user-submitted related servers found.

    Related Servers

    • Boring Gemini

      Boring206
      F
      license
      Not graded
      quality
      C
      maintenance
      An autonomous AI development agent that enables full-stack coding, automated verification, RAG-powered code search, and quality assurance through MCP tools. Supports Gemini CLI, Claude Code CLI, with features like parallel verification, security scanning, and spec-driven development.
      5
      -

    • Nexus-MCP

      jsagudelodev
      A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive Model Context Protocol toolkit that transforms AI assistants into autonomous agents capable of executing real-world tasks across filesystems, web requests, Git workflows, databases, system commands, and AI integrations.
      MIT

    • MCP Dev-Tools Agent

      naushadraien
      A
      license
      Not graded
      quality
      D
      maintenance
      A local AI agent system that gives any LLM real access to the filesystem, terminal, and codebase via MCP, usable as a standalone terminal agent or Continue.dev integration in VS Code.
      239 npm
      MIT

    • Coding Tools MCP

      xyTom
      A
      license
      Not graded
      quality
      B
      maintenance
      Empower any MCP-compatible AI Agent(MCP Client) with engineering-grade capabilities to understand, modify, run, and deliver real-world code repositories.
      465 PyPI
      1,125
      Apache 2.0

    • better-mcp

      erquier
      F
      license
      A
      quality
      B
      maintenance
      A universal MCP server that provides AI agents with structured tools for filesystem, database, shell, and git operations, enabling seamless interaction with projects.
      19
      -
    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.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: one initializes FastAPI, one initializes React, and one finalizes any newly created project. There is no functional overlap between them.

    Naming Consistency3/5

    The two initialization tools follow a similar pattern (framework_init_project), but the finalizer tool (just_project_runner) uses a completely different naming style. Additionally, one tool has the 'obox_' prefix while the other does not, causing inconsistency.

    Tool Count5/5

    Three tools is a well-scoped count for a project scaffolding server. Each tool serves a distinct purpose and the count is within the ideal 3-15 range.

    Completeness3/5

    The tool set covers the init and finalize lifecycle for FastAPI and React, but lacks support for other common frameworks and has no additional operations like listing projects or managing dependencies. The finalizer is somewhat disconnected from the init tools, requiring manual invocation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources