Can I use Groq as a CLI?

Yes. KosmoKrator exposes a Groq CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Groq through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Groq tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Groq credentials stored?

Groq credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Groq MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

Groq MCP Integration for CrewAI

Connect Groq to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 5 read 2 write API key auth

Submit Groq feedback View package source

Connect Groq to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Groq MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-groq": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=groq",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=groq --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Groq instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Groq Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Groq integration catalog.

MCP tool	Source function	Type	Description
`integration__groq__groq_list_models`	`groq.groq_list_models`	Read	List available Groq AI models. Returns model IDs, ownership, and other metadata for models accessible via the Groq API.
`integration__groq__groq_create_completion`	`groq.groq_create_completion`	Write	Create a chat completion using a Groq model. Send a list of messages and receive an AI-generated response with ultra-low latency. Supports configurable parameters like temperature, max_tokens, and top_p.
`integration__groq__groq_list_messages`	`groq.groq_list_messages`	Read	List messages in a Groq Cloud conversation. Returns message content, role, and metadata for each message in the conversation.
`integration__groq__groq_create_message`	`groq.groq_create_message`	Write	Create a message in a Groq Cloud conversation. Send a message with a specified role and content to a conversation.
`integration__groq__groq_list_files`	`groq.groq_list_files`	Read	List files uploaded to the Groq Files API. Returns file IDs, filenames, purposes, sizes, and upload timestamps.
`integration__groq__groq_get_file`	`groq.groq_get_file`	Read	Get metadata for an uploaded file in Groq, including its ID, filename, purpose, size in bytes, and processing status.
`integration__groq__groq_get_current_user`	`groq.groq_get_current_user`	Read	Get information about the currently authenticated Groq user, including user ID, email, and organization details.

Related Groq Pages

Groq CLIUse direct JSON commands instead of MCP discovery. Groq MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.