Skip to main content
Glama
Divinci-AI

opus-advisor-mcp

by Divinci-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to opus-advisor-mcp

No user-submitted related servers found.

    Related Servers

    • Consult LLM MCP

      raine
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that lets Claude Code consult stronger AI models (o3, Gemini 2.5 Pro, DeepSeek Reasoner) when you need deeper analysis on complex problems.
      1
      102 npm
      139
      MIT

    • codex-fusion-mcp

      Tritlo
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling Claude to consult Codex (GPT-5.x) mid-task for second opinions, plan/diff review, brainstorming, and codebase exploration via structured debates and permission-controlled interactions.
      2
      MIT

    • mcp-local-llm

      semenenkod333
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that allows Claude Code to offload mechanical tasks such as summarization, classification, and drafting to a local LLM, reducing API costs while keeping Claude in control of complex reasoning and quality review.
      14 npm
      MIT

    • codex-bridge

      ndcorder
      A
      license
      A
      quality
      D
      maintenance
      MCP server that lets Claude Code ask GPT Codex for adversarial planning, code review, debugging, research, and risk triage without leaving your project workflow.
      9
      13 npm
      2
      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

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a uniquely defined purpose: clearing the log, consulting Opus, reading the log, and reading metadata. No two tools overlap in functionality, so an agent can easily distinguish them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., consult_opus, read_advisor_log). The naming convention is uniform across the entire set.

    Tool Count5/5

    Four tools is a well-scoped count for an advisor MCP server. Each tool addresses a distinct need (consultation, log management, metadata access) without unnecessary extras.

    Completeness4/5

    The tool set covers the core operations: consultation, log reading/clearing, and metadata inspection. A minor gap is the lack of a configuration tool to adjust Opus parameters, but the current surface is sufficient for most workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources