TwitterShots · Model Context Protocol

Twitter Screenshot MCP

Create Twitter/X screenshots in your AI chat. Connect TwitterShots MCP to ChatGPT, Claude, Cursor, Codex, and other MCP clients.

Connect your AI →
Open Markdown version ↗

Remote setup requires no installation. TwitterShots account and screenshot quota required.

ChatGPT

@twittershots capture this https://x.com/elonmusk/status/2112931457786081428

TwitterShots · generate_screenshot
Screenshot of Elon Musk’s X post captured with TwitterShots

@twittershots X url → PNG screenshot → image URL

Connect TwitterShots to your AI

Choose your client below. Each guide includes setup, authorization, and a first tool call.

Authentication & requirements

The hosted TwitterShots MCP server uses OAuth over Streamable HTTP. There is nothing to install for a remote connection.

  1. Create a TwitterShots account and set up an active API key at https://twittershots.com/settings/keys. Screenshot generation requires available quota.
  2. Connect your client to the hosted URL and sign in with the same TwitterShots account. You do not need to paste your API key into the remote client.
  3. Authorize read:usage to check quota and create:screenshot to generate images. Each screenshot uses your account’s screenshot quota.

ChatGPT

Add TwitterShots as a custom MCP plugin and use it directly in a conversation. Availability depends on your account and workspace permissions.

  1. Open Plugins, select Add, then Add custom MCP server. If your interface uses Apps or Connectors, enable developer mode in its advanced settings and open the custom MCP connection form.
  2. Enter TwitterShots as the name, paste the server URL below, and choose OAuth. Create and install the plugin.
  3. Sign in with your TwitterShots account and approve access. In a new chat, type @ and select TwitterShots, then paste the example prompt.
text
https://mcp.twittershots.com/mcp
ChatGPT documentation ↗

Claude

Use the hosted server through a custom connector in Claude web or Desktop.

  1. Open Settings → Connectors → Add custom connector.
  2. Name it TwitterShots and enter the server URL below. Add the connector and complete the TwitterShots OAuth sign-in.
  3. Enable TwitterShots in the conversation’s tools menu. Ask Claude to check your quota, then generate a screenshot from a public post URL.
text
https://mcp.twittershots.com/mcp
Claude documentation ↗

Grok

Sign in to TwitterShots, then add a custom connector in Grok. Once connected, Grok can check your screenshot quota and create PNG screenshots of public X posts from your chats.

  1. Open grok.com/connectors.
  2. Click New Connector, select Custom, and name it TwitterShots.
  3. Paste the MCP server URL below.
  4. Complete OAuth sign-in with your TwitterShots account, then ask Grok to check your quota or generate a screenshot.
text
https://mcp.twittershots.com/mcp
Grok documentation ↗

Grok Bot

Paste this prompt into Grok Bot to get started with TwitterShots MCP.

  1. Send the prompt below to Grok Bot.
  2. Follow Grok Bot’s instructions to add the TwitterShots connector and sign in to authorize access.
text
read https://twittershots.com/mcp and setup twittershots mcp

Cursor

Give Cursor Agent access to tweet screenshots with a project or global MCP configuration.

  1. Add the configuration below to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects.
  2. Open Cursor’s MCP settings, enable TwitterShots, and complete OAuth when prompted.
  3. In Agent chat, ask Cursor to use TwitterShots to create a screenshot and return its image URL.
json
{
  "mcpServers": {
    "twittershots": {
      "url": "https://mcp.twittershots.com/mcp"
    }
  }
}
Cursor documentation ↗

Claude Code

Register the remote HTTP server from your terminal.

  1. Run the command below in your terminal.
  2. Start Claude Code and run /mcp. Select TwitterShots and finish the browser sign-in.
  3. Ask Claude Code to check TwitterShots authorization and quota before generating your first image.
shell
claude mcp add --transport http twittershots https://mcp.twittershots.com/mcp
Claude Code documentation ↗

Codex

Connect the Codex CLI to the hosted server with OAuth.

  1. Run the commands below to add TwitterShots and sign in.
  2. Complete authorization in your browser, then open a new Codex session.
  3. Ask Codex to use TwitterShots to capture a public X post. The MCP configuration is stored in ~/.codex/config.toml.
shell
codex mcp add twittershots --url https://mcp.twittershots.com/mcp
codex mcp login twittershots
Codex documentation ↗

VS Code / GitHub Copilot

Configure an HTTP MCP server in your workspace.

  1. Save the JSON below in .vscode/mcp.json.
  2. Start the server from VS Code’s MCP controls and authorize TwitterShots in your browser.
  3. Open Copilot Chat in Agent mode, enable the TwitterShots tools, and request a screenshot.
json
{
  "servers": {
    "twittershots": {
      "type": "http",
      "url": "https://mcp.twittershots.com/mcp"
    }
  }
}
VS Code / GitHub Copilot documentation ↗

Available MCP tools

Once connected, your assistant can discover these tools from the server.

  1. authorization_status — check whether the connection has the required permissions.
  2. get_api_usage — check your remaining screenshot quota.
  3. generate_screenshot — create one PNG from a public X/Twitter post URL or numeric ID. Choose light or dark theme and auto, 1:1, 4:5, 5:4, 16:9, or 9:16 aspect ratio. Returns a publicly accessible image URL.

Create your first screenshot

After connecting, paste this prompt into your AI conversation. Replace the example URL with your public post.

  1. Confirm that authorization_status succeeds and get_api_usage reports available quota.
  2. Ask the assistant to call generate_screenshot and return the actual image URL from the tool response.
text
Use TwitterShots to check my remaining quota, then create a dark, square PNG screenshot of https://x.com/elonmusk/status/2108321181602353333 and return the image URL.

If the connection fails

Check the connection before retrying screenshot generation.

  1. Sign-in or permission error: reconnect TwitterShots and complete OAuth again. Run authorization_status to verify access.
  2. No quota or no active key: open https://twittershots.com/settings/keys and check your account’s API key and usage.
  3. Tools missing: enable TwitterShots in the chat, refresh the MCP tool list, or restart the client after changing its configuration.
  4. Screenshot fails: use a public X/Twitter post URL or numeric ID. Private, deleted, or unavailable posts cannot be captured.
  5. Client cannot connect: confirm the URL ends in /mcp and the remote client supports Streamable HTTP and OAuth.