Included with Pro

MCP connector

PostCapture runs a remote Model Context Protocol server. Add it to Claude, ChatGPT, Claude Code, Cursor or any other MCP client, sign in once, and your agent can turn post links into finished screenshots.

Server URL: https://postcapture.com/mcp
Sign in: OAuth with your PostCapture account. No API key.
Plan: Pro, 500 screenshots a month shared with the dashboard and the API.

What you can ask for

Once connected, you talk to the agent as usual. It picks the tool, fills in the settings and hands you the image. A few prompts that work well:

"Screenshot https://x.com/larsbuilds/status/2078434601924485623 with the dark theme and no background."
"Make a screenshot of this TikTok for the newsletter, keep it portrait and add a soft shadow."
"How many PostCapture screenshots do I have left this month?"

Set it up

Every client needs the same two things: the server URL and a sign-in. Pick yours below. When the client opens PostCapture in the browser, sign in and approve the connection. That is the whole setup.

https://postcapture.com/mcp

Claude (web and desktop)

Open Settings, then Connectors.
Choose Add custom connector. Name it PostCapture and paste the server URL. Leave the client ID and secret empty.
Click Connect, sign in to PostCapture in the tab that opens, and approve.
In a new chat, make sure PostCapture is enabled under the tools menu, then paste a post link.

Custom connectors are available on paid Claude plans.

Claude Code

Add the server from the terminal:

1claude mcp add --transport http postcapture https://postcapture.com/mcp

Then start a session and run /mcp. Pick PostCapture and follow the sign-in link. Add --scope user to the command above if you want the connector in every project rather than just the current one.

ChatGPT (web)

PostCapture is not in the ChatGPT app directory, so you add it as a custom MCP app. That needs Developer mode.

Open Settings, then Plugins. At the bottom, open Developer mode and click Enable Developer mode.
Go to chatgpt.com/plugins, click the plus icon in the top right, then Create App and Create MCP App.
Name it PostCapture. Under Connection, keep Server URL selected and paste the server URL. Set Authentication to OAuth and leave the advanced OAuth settings as they are.
Tick I understand and want to continue and click Create.
Click Sign in with PostCapture and approve in the window that opens.

ChatGPT (desktop app)

Open Settings, then Plugins. Click Add, then Add MCP Server.
Choose Streamable HTTP, paste the server URL, and click Add.
Back in Plugins, open MCP and click Authenticate next to PostCapture. Approve in the browser.

Cursor

Add the server to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json inside one project:

1{
2  "mcpServers": {
3    "postcapture": {
4      "url": "https://postcapture.com/mcp"
5    }
6  }
7}

Open Cursor Settings, go to MCP, and click the sign-in prompt next to PostCapture. Approve in the browser and the tools appear in the agent.

VS Code

Create .vscode/mcp.json in your workspace, or add the server to your user settings through the MCP: Add Server command:

1{
2  "servers": {
3    "postcapture": {
4      "type": "http",
5      "url": "https://postcapture.com/mcp"
6    }
7  }
8}

Click Start above the server entry. VS Code asks you to allow the sign-in, opens PostCapture, and stores the connection. The tools are then available in agent mode.

Other clients

Any client that supports remote servers over Streamable HTTP with OAuth works. Use the server URL and let the client discover the rest: clients register themselves through Client ID Metadata Documents or dynamic client registration, and sign in uses OAuth 2.1 with PKCE. To poke at the server directly, run npx @modelcontextprotocol/inspector, choose Streamable HTTP, paste the URL and click Open Auth Settings, then Quick OAuth Flow.

What you approve

The consent screen names the client and asks for two permissions. Approving needs an active Pro plan on the account you sign in with.

screenshots:create: Render screenshots, which uses your monthly allowance.
screenshots:read: Read your plan, usage and the list of render settings.

The connector never sees your password, and it cannot manage your account, billing or API keys. Disconnect it in the client at any time to revoke access.

Tools

create_screenshotneeds screenshots:create: Renders a post URL into a PNG and returns the image plus a download URL that stays valid for about an hour. Takes the same settings as the Screenshot API. Pass the same idempotencyKey on a retry and you get the first result back instead of a second render and a second charge.
get_account_usageneeds screenshots:read: Your plan and this month's screenshots: limit, used, remaining and when the allowance resets.
list_screenshot_optionsneeds screenshots:read: The supported platforms and the full JSON Schema of the settings create_screenshot accepts, with their defaults. Agents call this on their own when you ask for a specific look.

Usage and limits

Each successful screenshot uses one of your 500 monthly screenshots. A failed render uses none. The allowance is shared with the dashboard and the API.
Screenshot requests share your account's rate limit of 10 per minute with your API keys.
The connection keeps working only while the account is on Pro. If Pro ends, requests are refused until you upgrade again.
A connection lasts as long as the PostCapture sign-in you approved it from. Signing out of that browser, or not opening PostCapture there for 90 days, disconnects it. The client then asks you to connect again.
Renders appear in your dashboard history, marked MCP.

Troubleshooting

The client says the connection was refused, or the consent screen asks me to upgrade.: The connector needs an active Pro plan on the account you sign in with. Upgrade from the billing page, then connect again.
A tool returns insufficient_scope.: The connection was approved without one of the two permissions. Remove the connector in your client and add it again, then leave both boxes ticked on the consent screen.
It worked for weeks and now asks me to sign in again.: A connection lives as long as the PostCapture browser session you approved it from. Signing out there, or not opening PostCapture in that browser for 90 days, ends it. Sign in again and the client reconnects.
A render fails with rate_limited.: Your account gets 10 screenshot requests per minute across the connector and every API key. Wait a minute and retry, or ask the agent to space the calls out.
The agent says the screenshot was made but I cannot find it.: Every MCP render shows up in your dashboard history marked MCP. The download URL in the tool result expires after about an hour, so save the image if you need it later.