1. Remote MCP Server

Connect an MCP client that supports remote Streamable HTTP and OAuth to https://mcp.twittershots.com/mcp. Sign in with your TwitterShots account when your client prompts you to authorize the connection. You do not need to paste an API key into the client.

For clients that accept an MCP server URL in JSON, the connection looks like this (the settings location varies by client):

{
  "mcpServers": {
    "twittershots": {
      "url": "https://mcp.twittershots.com/mcp"
    }
  }
}

The connection requests read:usage to check quota and create:screenshot to generate images. A TwitterShots account with an active API key and available quota is required for screenshot creation; the MCP connection finds the key linked to your account after OAuth authorization.

Available tools

  • authorization_status checks whether the connection has the required permissions.
  • get_api_usage reports your remaining screenshot quota.
  • generate_screenshot creates one PNG from a public X/Twitter post URL or numeric ID. It supports light or dark theme and auto, 1:1, 4:5, 5:4, 16:9, or 9:16 aspect ratios. It returns a publicly accessible image URL and uses screenshot quota.

Try: “Create a dark, square screenshot of https://x.com/elonmusk/status/2108321181602353333.”

2. Local MCP Server (Node.js)

You can still run the original MCP server on your own computer. This option uses a TwitterShots API key instead of the remote server's OAuth sign-in.

  1. Get an API key from Account Settings.
  2. Clone and build the local server:
git clone https://github.com/twittershots/twittershots-mcp.git
cd twittershots-mcp
npm install
npm run build
  1. Add it to your MCP client configuration. Replace the path and API key with your own values:
{
  "mcpServers": {
    "twittershots": {
      "command": "node",
      "args": ["/path/to/twittershots-mcp/build/index.js"],
      "env": { "TWITTERSHOTS_API_KEY": "your-api-key-here" }
    }
  }
}

Resources