Grok
Grok is xAI's API platform for text, image, video, embedding, file, search, and voice capabilities.
Verdict
Common use cases
- Draft blog posts with reasoning traces
- Generate hero images for landing pages
- Embed knowledge-base articles for search
- Synthesize research summaries from transcripts
- Prototype video concepts from text prompts
Integration
- Vendor
- Grok
- Category
- other
- Auth
- API_KEY
- Tools
- 8
- Composio slug
grok
Tools
- Create Embeddings
Create vector embeddings for one or more text inputs with an xAI embedding model.
- Create Response
Generate a bounded, non-streaming Grok response from text or structured multimodal input, with optional reasoning, search, and function or web-search tools. Responses are ephemeral by default; set store=true to retain one for 30 days.
- Generate Image
Generate one or more images from a text prompt with an xAI image-generation model.
- Generate Video
Start asynchronous xAI video generation from a text prompt, optionally conditioned on an image, and return a request ID for status checks.
- Get API Key Info
Inspect the connected xAI API key's identity, wildcard or granular ACLs, and key or team blocking state.
- Get Current Account
Verify the connected xAI credential and return the caller, team, zero-data-retention status, and key blocking state.
- Get Video
Check an asynchronous xAI video request. Returns pending while generation is in progress, the video and usage when done, or the structured generation error when failed.
- List Models
List models available to the connected xAI key, including model IDs and published pricing metadata needed to choose a model for other tools.
Setup
Setup guide
- 11. In Switchy, navigate to Settings → Integrations → MCP Servers and click Add Server. 2. Select Grok from the catalog and choose API Key authentication. 3. Visit console.x.ai, sign in, and generate a new API key with access to the models you plan to use. 4. Paste the key into Switchy's configuration modal and click Connect. 5. Switchy will verify the key by calling Get Current Account and display your team name and zero-data-retention status. 6. Open any Project and type '@Grok list the models I can use' to confirm the connection works. 7. The response will enumerate available text, image, video, and embedding models along with pricing metadata. 8. To invoke a tool, @mention Grok and describe your task — for example '@Grok generate an image of a mountain sunset' or '@Grok create embeddings for these three paragraphs'.
What teammates see: by default, memories from Grok are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Draft Product Announcement
@Grok write a 300-word product announcement for a new API analytics dashboard. Enable reasoning so I can see your thought process.
Create Social Media Asset
@Grok generate a 1024×1024 image showing a diverse team collaborating around a whiteboard, modern office aesthetic, natural lighting.
Embed Documentation Corpus
@Grok create embeddings for these five support articles so I can index them for similarity search.
Check Video Generation Status
@Grok check the status of video request ID vid_abc123xyz and return the download URL if it's ready.
Compare Model Pricing
@Grok list all text and image models I have access to, including input and output pricing per token.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Grok list all available models with their pricing and show me which ones support vision input
Here are the models available on your xAI account: **Text Models:** - grok-beta (128k context, $5/1M input tokens, $15/1M output) - grok-vision-beta (128k context, vision-capable, $5/1M input tokens, $15/1M output) **Embedding Models:** - grok-embedding-1 (8k context, $0.10/1M tokens) **Image Generation:** - grok-2-image-1 ($0.05 per image) The grok-vision-beta model supports multimodal input including images. All pricing is current as of your API key's access level.
This example shows the List Models tool, which is essential for understanding what capabilities your API key can access. Model availability and pricing can change; the MCP returns live data from xAI's API. Useful for cost estimation before running expensive operations like video generation or high-volume embedding jobs.
@Grok generate an image of a minimalist workspace with a laptop, coffee mug, and morning light through a window
Image generated successfully. The xAI image model produced a 1024×1024 rendering showing a clean desk with a silver laptop, white ceramic mug, and soft natural light casting shadows across the surface. The composition uses a muted color palette with warm highlights. **Usage:** 1 image generated, $0.05 charged to your account. The image is available for download and has been stored temporarily. Note that xAI image generation is synchronous—this request completed in approximately 8 seconds.
Demonstrates the Generate Image tool for visual content creation. Unlike video generation, image requests are synchronous and return immediately. Be aware that image generation costs accumulate quickly with multiple requests, and xAI's content policy applies—prompts violating guidelines will be rejected before generation starts.
@Grok start generating a 5-second video of ocean waves at sunset, then check the status and let me know when it's ready
Video generation started. Request ID: `vid_abc123def456` Initial status: **Pending** — xAI is processing your request. Video generation typically takes 2-5 minutes depending on queue depth. *[After polling with Get Video tool]* Status update: **Completed** — Your 5-second video is ready. The clip shows rhythmic ocean waves with orange and pink sunset reflections. Video resolution: 1280×720, format: MP4. **Usage:** 5 seconds generated, $0.50 charged to your account ($0.10/second). Video generation is asynchronous, so you'll need to poll for completion or set up a workflow to check back periodically.
Showcases the async video workflow using Generate Video and Get Video tools together. Video generation is significantly more expensive than images ($0.10/second) and requires polling to check completion status—the MCP doesn't automatically wait. Plan for 2-5 minute delays and handle pending states in your automation logic.
Use-case deep-dives
When Grok's embeddings beat a dedicated vector service for small teams
A 6-person support team wants to embed 2,000 help articles so agents can search by semantic similarity during live chats. Grok's Create Embeddings tool handles this in one API call with no infrastructure setup—no Pinecone account, no separate embedding pipeline. The trade-off: you're locked into xAI's embedding model and pricing, and there's no built-in vector store, so you'll still need a lightweight database like SQLite with pgvector or Supabase to hold the results. If your corpus grows past 10,000 documents or you need sub-100ms retrieval, a dedicated vector service becomes worth the setup cost. For teams under that threshold who already use Grok for chat, consolidating embeddings here cuts one vendor and one auth flow.
Grok's image and video tools for rapid campaign prototyping
A 3-person growth team needs 20 social-media variants and 5 short-form video concepts for a product launch in 48 hours. Grok's Generate Image and Generate Video tools let them prompt, iterate, and export without leaving the Switchy workspace or juggling Midjourney and Runway accounts. The video tool is asynchronous—you kick off generation, poll with Get Video, and retrieve the file when ready—so it fits batch workflows better than real-time editing. The catch: xAI's models are general-purpose, not fine-tuned for brand consistency, so expect to spend 10-15 minutes per asset on prompt refinement. If your brand guidelines are strict or you need frame-level control, dedicated creative tools still win. For fast, low-fidelity prototyping where speed trumps pixel-perfect output, Grok closes the loop in one MCP.
Using Grok's account and model tools to track xAI spend across projects
A 12-person engineering org runs Grok calls from three different projects—chatbot backend, internal docs search, and a prototype reasoning agent. The Get Current Account and List Models tools surface which API keys are hitting which models, plus per-model pricing metadata, so the team lead can attribute costs without parsing raw billing CSVs. Get API Key Info exposes ACL scopes, which matters when you want to lock a staging key to embeddings-only or block a deprecated key before it racks up charges. The limitation: these are read-only inspection tools, not cost-control levers—you can't set spend caps or auto-rotate keys from the MCP. If your monthly xAI bill is under $500, this visibility is enough to catch runaway usage. Above that threshold, you'll want xAI's dashboard or a third-party spend tracker.
Frequently asked
What does the Grok MCP let me do in Switchy?
It connects your team to xAI's Grok models for text generation, image creation, video generation, and embeddings. You can ask Grok questions with web search enabled, generate images from prompts, kick off async video renders, and create vector embeddings—all without leaving your Switchy workspace. Responses are ephemeral by default unless you configure storage.
Do I need a paid xAI account to use this MCP?
Yes. You need an xAI API key with sufficient credits and the right ACLs. The MCP includes a Get API Key Info tool that shows your key's permissions and blocking state, so you can verify access before running expensive operations like video generation. Free-tier keys won't work for most production use cases.
Can the Grok MCP generate videos longer than 5 seconds?
That depends on xAI's current model limits, not the MCP itself. The Generate Video tool starts an async job and returns a request ID; you then poll with Get Video until it's done. If xAI's models cap video length at 5 seconds today, the MCP won't bypass that. Check xAI's pricing page for current duration limits.
Why use this MCP instead of calling xAI's API directly?
The MCP wraps xAI's endpoints in a conversational interface your team can use without writing code. Non-technical teammates can generate images, run searches, or create embeddings by describing what they need. You also get unified audit logs and cost tracking across all your Switchy integrations, which raw API calls don't provide.
Who on my team should connect the Grok MCP?
Whoever holds your xAI API key and understands your usage budget. Video and image generation burn credits fast, so the person connecting it should know how to set rate limits or monitor spend. Once connected, you can grant workspace members access to specific tools—like embeddings only—without sharing the raw key.