Get the FREE Ultimate OpenClaw Setup Guide →

compound

Groq Compound Beta MCP Server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio groq-compound-mcp-server npx -y groq-compound-mcp-server \
  --env GROQ_API_KEY="YOUR_GROQ_API_KEY_HERE"

How to use

The groq-compound-mcp-server provides an MCP (Model Context Protocol) server for interacting with Groq models, including compound and meta models. It exposes tools such as ask_with_realtime_information and ask_with_code_execution to enable dynamic querying and code execution capabilities against Groq models. The server is designed to be run via standard MCP client tooling using stdio transport, allowing clients like Claude Desktop or custom MCP clients to connect and issue model-context-related requests. To start, run the server using npx groq-compound-mcp-server (or groq-compound-mcp-server if installed globally) and configure your MCP client to connect to the server's stdio stream as described in the MCP Quickstart for Server Developers. The server requires a Groq API key and will use it to authenticate requests to Groq services.

How to install

Prerequisites:

  • Node.js >= 18.0.0
  • npm (comes with Node.js)

Installation steps:

  1. Install the MCP server package:
npm install groq-compound-mcp-server
  1. Verify installation (optional):
npx groq-compound-mcp-server --version
  1. Prepare environment variables (example):
export GROQ_API_KEY=YOUR_GROQ_API_KEY_HERE
  1. Start the server (see how_to_use for client configuration):
npx groq-compound-mcp-server

Prerequisites recap: Ensure Node.js v18+ is installed and you have a valid GROQ_API_KEY in your environment before starting the server.

Additional notes

Environment variables and config tips:

  • GROQ_API_KEY is required for authenticating with Groq services.
  • REDIS_URL is recommended if you plan to use SSE transport (as noted for Vercel deployments); configure it in your environment or MCP client settings if your workflow depends on SSE transport.
  • When running locally, you can specify the GROQ_API_KEY directly in an mcpServers config block (as shown in the example) or rely on your shell/environment for GROQ_API_KEY.
  • If you deploy to platforms like Vercel, follow the platform-specific steps to set environment variables and ensure the server is invoked via the standard MCP transport path.

Related MCP Servers

Sponsor this space

Reach thousands of developers