Counsel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port (HTTP mode) | 3000 |
| COUNSEL_API_KEY | No | Your API key from counsel.getmason.dev (required for STDIO mode) | |
| COUNSEL_API_URL | No | Counsel API base URL | https://counsel.getmason.dev |
Instructions
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.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_consultationD | – |
| get_consultation_statusD | – |
| get_consultation_reportD | – |
| list_consultationsD | – |
| sharpen_questionD | – |
| consult_advisorD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools have mostly distinct purposes centered around consultation management: starting consultations, checking status, getting reports, listing them, sharpening questions, and consulting an advisor. There is some potential overlap between 'consult_advisor' and 'start_consultation' as both might initiate interactions, but the naming suggests different phases or modes of consultation.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. The verbs are clear and appropriate (consult, get, list, sharpen, start), and the nouns consistently relate to consultations or related concepts like advisor, report, status, and question.
With 6 tools, the count is reasonable for a consultation-focused server. It covers core operations without being overly sparse or bloated. A slight deduction because, without descriptions, it's unclear if all tools are essential, but the scope appears well-defined.
The tools suggest a consultation lifecycle with start, status, report, and list operations, plus question refinement and advisor consultation. However, without descriptions, gaps are uncertain—for example, there's no clear update or delete tool for consultations, which might be needed for full lifecycle management. The surface seems functional but potentially incomplete.