groq-compound-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_URL | No | Connection URL for a Redis instance (recommended for SSE transport). | |
| GROQ_API_KEY | Yes | Your Groq API key. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_with_realtime_informationB | Ask a question requiring real-time information (e.g., news, current events) using a Groq model. |
| ask_with_code_executionA | Ask questions that benefit from Python REPL interaction (e.g., for intermediate calculations or code execution). |
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 2 tools
Each tool has a clearly distinct purpose: one for code execution, the other for real-time information. No overlap in functionality.
Both tools follow a consistent 'ask_with_' prefix pattern, making it predictable for agents to select the right tool.
Two tools is slightly thin for a 'compound' server, but each tool covers a distinct, specialized need. The count is reasonable but could be expanded.
The server covers code execution and real-time info, but lacks a general knowledge query tool. This is a notable gap for a question-answering server.