AI agents MCP

connect yourown ai agent.

Claude Code and other MCP clients can send Pollux your photos and post ideas, and suggest when they go out. You still approve every post.

Works on every paid Pollux plan. Your keys are in YOU › Settings › AI agents.

How it works Three steps

  1. make a key.

    In YOU › Settings › AI agents, tap Create a key. Copy the key: Pollux shows it only once.

  2. add pollux.

    In Claude Code, run this once in your terminal, with your key in place of YOUR_KEY:

    claude mcp add --scope user --transport http pollux https://pollux.team/api/mcp --header "Authorization: Bearer YOUR_KEY"

    Another MCP client? Add https://pollux.team/api/mcp with the header Authorization: Bearer YOUR_KEY.

  3. just ask.

    Your agent sends the studio a brief. We make the post, and it waits until you tap Approve all in Pollux.

Examples In your words

for example.

  • Send these 5 photos to Pollux as one post about last night’s dinner, best time tomorrow morning.
  • What’s on my Pollux calendar this week?
  • Which of my Pollux posts are waiting for my approval?

What it can do You decide

you stay in charge.

It can

  • See your plan, its limits and your connected networks
  • See your briefs, posts and calendar
  • Send briefs with photos and videos, with a preferred time
  • See trend cards
  • Read your Replies cards: only if you tick Read my Replies cards, on plans with Replies

It can’t

  • Approve, publish, stop or delete a post
  • Send, hide or skip a reply
  • Connect or disconnect a network
  • Change your settings or your plan
  • Every post made from your agent’s brief waits until you tap Approve all in Pollux. TikTok asks you to confirm each post.
  • Your agent’s time is a preferred time: the studio plans for it and aims to send you the preview before it. The post goes out when you tap Approve all.
  • If your agent says its photos or videos were made or changed with AI, the post is labelled AI-generated.

You choose what each key may do when you make it, and you can make a separate key for each agent.

Safety Your key

keep your key safe.

  • Treat the key like a password. Run the command in your terminal yourself, and never paste the key into a chat (a chat with an AI included) or into code you share.
  • Revoke a key any time in YOU › Settings › AI agents with Revoke: the agent stops at once.
  • Replies cards hold other people’s comments and messages. Tick them only for an agent you trust with them: what your agent receives falls under its AI provider’s terms.
  • We log each call (the time, the tool and the result), never what it carried, and keep the log for 90 days.
  • Each key can make up to 60 requests a minute and 1,000 an hour, and all your keys together up to 120 a minute and 3,000 an hour. Uploads, briefs and links have their own limits. We may revoke a key that is misused.

For developers REST and MCP

for developers.

The same tools over REST, with your key on every request.

Base URL
https://pollux.team/api/v1
MCP server
https://pollux.team/api/mcp
Header
Authorization: Bearer YOUR_KEY
Format
JSON · ISO 8601 UTC
Limits
Up to 60 requests a minute and 1,000 an hour per key, and 120 a minute and 3,000 an hour for all your keys together
Over a limit
HTTP 429 · Retry-After

Uploads, briefs and links have their own limits too. Over one of them, an MCP tool answers with a tool error that gives retry_after_sec, not with HTTP 429.

MethodPathWhat it doesScopeMCP tool
GET/accountYour plan, its limits and usageaccount:readpollux_get_account
GET/channelsYour connected networksaccount:readpollux_list_channels
GET/briefsThe briefs you sentposts:readpollux_list_briefs
POST/briefsSend a briefposts:writepollux_submit_post
POST/briefs/{brief_id}/scheduleSet or change a brief’s preferred timeposts:writepollux_schedule_post
GET/postsPosts of the last 14 days, per networkposts:readpollux_list_posts
GET/calendarBriefs and posts in time orderposts:readpollux_get_calendar
POST/uploadsA place to upload one photo or videoposts:writepollux_create_upload
GET/repliesReplies cards, read onlyreplies:readpollux_list_replies
GET/trendsTrend cardstrends:readpollux_list_trends

Try it:

curl https://pollux.team/api/v1/account -H "Authorization: Bearer YOUR_KEY"

Clients that can only sign in with OAuth can’t connect yet: use one that sends the header.

May we measure our ads? If you accept, the ad platforms we advertise on get cookie IDs, the pages you view here and, when you buy, a hashed copy of your email. If you reject, nothing is shared and the site works the same.