Schema | opus-advisor-mcp

opus-advisor-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`ADVISOR_LOG_DIR`	No	Override the log directory (default: ~/.opus-advisor/<project>-<hash>/)

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
consult_opusA	Consult Claude Opus 4.7 for strategic advice. Opus runs via the Claude Code CLI with your existing subscription — no API key needed. The advisor maintains a per-project consultation log for continuity across calls. History is capped by both entry count (5) and token budget (~6K tokens) to prevent context bloat. Use this for architecture decisions, complex debugging, code review, or any problem that benefits from deeper reasoning.
read_advisor_logA	Read the consultation log from prior Opus advisor calls for this project. Useful for reviewing past advice or getting context on decisions already made.
read_advisor_metaA	Read structured metadata (latency, token counts, effort levels) from all consultations. Useful for understanding cost and performance patterns.
clear_advisor_logA	Clear the consultation log and metadata to start fresh for this project.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Divinci-AI/opus-advisor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server