groki-mcp

# Groki MCP

Give AI agents a meme factory, not another blank canvas.

Groki MCP turns a compact creative brief into **nine private, editable meme directions**: three visual templates across Relatable, Savage, and Unhinged tones. Agents can then inspect a draft, refine exact text or variant choices, and check the connected account's credit balance.

## Remote endpoint

```text
https://www.groki.meme/api/mcp
```

- Transport: Streamable HTTP
- Authentication: OAuth 2.1 with PKCE and dynamic client registration
- Required scopes: `meme:drafts`, `meme:credits`
- Product and OAuth guide: https://www.groki.meme/agents

MCP-compatible clients should connect to the endpoint and complete the OAuth authorization flow. Do not paste personal access tokens into client configuration.

## Tools

| Tool | What it does |
| --- | --- |
| `create_meme_draft` | Creates nine private meme directions from a brief. One batch costs one Groki credit after a complete brief is supplied |
| `get_meme_draft` | Reads an active private draft and its variants for the connected account |
| `update_meme_draft` | Applies deterministic text, variant, or brief edits without AI-generation cost |
| `get_credit_balance` | Reads the connected Groki account's available credits |

## Example brief

```text
Create memes about a Friday production deploy that failed. Make the humor sharp but not mean. Write in English.
```

The agent should ask Groki to create the draft, review the alternatives with the user, and only then choose or edit a variant.

## Safety and privacy

- Drafts are private to the connected Groki account
- Generating a complete nine-direction batch costs one credit
- Incomplete briefs return clarification questions without charging
- Updates use optimistic concurrency to prevent an agent from silently overwriting another edit

## Registry metadata

The canonical MCP Registry manifest is [`server.json`](./server.json). This repository documents the hosted integration; the product source is not included here.