Skip to main content
Glama
Sign In
BlackBox-MCP

BlackBox-MCP

by mshanghai570
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to BlackBox-MCP

No user-submitted related servers found.

    Related Servers

    • pollux-mcp

      Wsyjq
      A
      license
      A
      quality
      B
      maintenance
      MCP server for local-first project memory, enabling AI agents to log, search, and retrieve structured project history, summaries, and per-file dossiers with client-specific configuration and diagnostics.
      15
      1
      MIT

    • Sugar

      Sitas17424
      F
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP memory server that lets AI coding agents store, search, and recall project-specific and cross-project knowledge, so architecture decisions, preferences, error patterns, and coding guidelines persist across sessions. It also exposes optional task-queue tools for handing off autonomous work that draws on the same stored context.
      -

    • knitbrain

      PDgit12
      A
      license
      A
      quality
      C
      maintenance
      Local-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.
      37
      65 npm
      6
      MIT

    • Concordia

      Zorabi
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first MCP server for coordinating Codex and ZCode agents, enabling task management, event tracking, and optional cross-machine Redis relay.
      19 npm
      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

    B3.4/5.0

    Scored across 35 tools

    Disambiguation4/5

    Tools are generally distinct: assistant CRUD, task delegation, memory, provider management all have clear boundaries. Some potential overlap exists between task delegation modes (delegate_task vs parallel_task vs debate_task vs pipeline_task), but descriptions clarify their distinct purposes. The enable/disable_assistant pair could be confused with update_assistant(enabled=...), but not severely.

    Naming Consistency4/5

    Mostly consistent verb_noun pattern (list_assistants, create_assistant, delegate_task, save_memory). A few deviations exist: blackbox_status and blackbox_help use a prefix instead of verb_noun, and agent_handoff is a noun without a clear verb. However, the vast majority follow the expected convention.

    Tool Count3/5

    35 tools is on the heavy side for a single server, though the domain is broad (assistants, tasks, memory, providers, approvals, project scanning). Some functions could be merged (e.g., enable/disable_assistant could be handled by update_assistant), and the task delegation variants might be consolidated. It's borderline but not egregious.

    Completeness5/5

    Coverage is comprehensive: full CRUD for assistants, providers, and memory; task lifecycle includes delegation, listing, retrieval, cancellation, and multiple modes (parallel, review, debate, pipeline); approvals and configuration are included. No obvious gaps for the stated purpose of coordinating AI assistants.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources