Pincast
API/Connect an MCP client

Connect an MCP client

Reach every Pincast tool from Claude Code, or any MCP client, with one API key.

Every tool in the registry answers on the MCP endpoint, with the same key and the same authorization as the REST API. Nothing else is exposed: the key resolves the organization, so a tool input never carries one.

The endpoint

https://pincast.io/api/mcp

It speaks streamable HTTP. GET, POST and DELETE all land on the same handler, which is what an MCP client expects.

Create a key

/orgs/{orgSlug}/settings/api-keys

Send it as a bearer token or as x-api-key; both reach the same handlers.

Claude Code

claude mcp add --transport http pincast https://pincast.io/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Then claude mcp list shows pincast connected, and the tools appear in the session.

What you can then ask for

The tools are the ones listed in Tools API. In practice:

  • publish an image pin now or on a date - create_pin
  • render a video from a still and publish it - generate_video, then create_video_pin (see Videos API)
  • read what is queued, published or failed - list_pins, get_pin
  • find the account and board ids a pin needs - list_accounts, list_boards
  • read impressions, saves and outbound clicks - get_analytics

A write tool does exactly what the same button in Pincast does: the pin is queued, paced and retried the same way, and shows up in the same lists.

Tools APIAuth Components