Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"groq-compound": {
"env": {
"GROQ_API_KEY": "YOUR_GROQ_API_KEY_HERE"
},
"args": [
"-y",
"groq-compound-mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Provides a Model Context Protocol (MCP) server for interacting with Groq models, including compound/meta models.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'groq-compound-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked groq-compound-mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
MCP Security Weekly
Get CVE alerts and security updates for Compound Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Provides a Model Context Protocol (MCP) server for interacting with Groq models, including compound/meta models.
This server exposes the following tools:
ask_with_realtime_informationask_with_code_executionGROQ_API_KEY environment variable.npm install groq-compound-mcp-server
This server follows the standard MCP server pattern using stdio for transport. It's designed to be run by an MCP client (like Claude Desktop or a custom client).
Refer to the official MCP Quickstart for Server Developers for instructions on setting up and connecting MCP servers.
When configuring your client, use the command npx groq-compound-mcp-server or groq-compound-mcp-server (if installed globally) to run this server.
Here's an example of how you might configure an MCP client (e.g., in a settings.json file) to launch this server:
{
"mcpServers": {
"groq-compound": {
"command": "npx",
"args": [
"-y",
"groq-compound-mcp-server"
],
"env": {
"GROQ_API_KEY": "YOUR_GROQ_API_KEY_HERE"
}
}
}
}
This server can also be deployed to Vercel.
Prerequisites:
Environment Variables: Set the following environment variables in your Vercel project settings:
GROQ_API_KEY: Your Groq API key.REDIS_URL: (Recommended for SSE transport) The connection URL for a Redis instance (e.g., from Vercel KV or Upstash).Build Configuration:
Vercel should automatically detect it as a Next.js application. The build command npm run build:vercel (or yarn build:vercel/pnpm build:vercel) and the output directory (.next) will be used.
Accessing the MCP Server:
Once deployed, your MCP server endpoints will be available at https://your-deployment-url.vercel.app/api/mcp.
For example, the SSE endpoint would be https://your-deployment-url.vercel.app/api/mcp/sse.
To run the Vercel deployment locally:
npm install -g vercel.env.local file at the project root):
GROQ_API_KEY=your_groq_api_key
REDIS_URL=your_redis_url
vercel dev or npm run dev:vercel.