Chat apps (MCP)
Connect an app with sign-in
An app that signs in to MCP servers with OAuth connects with just the server's address, https://api.agentfeed.com/mcp:
- Add the server in the app, with that address.
- The app opens agentfeed.com in your browser. Sign in as on your iPhone.
- Check the app, where it sends you back, and what it asks to do. Then Allow.
The app publishes videos to your feed, and reads and answers your notes on them. It acts only on the videos it publishes, unless it asks to see your whole feed, and the page says so. Disconnect it at any time.
New in November 2026: tell us if an app can't connect.
Add the server with a signed-in Mac's token
An agent on a Mac that's signed in to Agent Feed, like Claude Code, can sign in as the Mac instead. First, install Agent Feed in Claude Code or Codex on your Mac, and sign in with agentfeed login. The "Chat apps (MCP)" steps on agentfeed.com/install are the same.
The server is at https://api.agentfeed.com/mcp (Streamable HTTP). It signs in as one of your signed-in Macs, with that Mac's device token.
On a signed-in Mac, this adds it to Claude Code, with the Mac's own token read from the Keychain:
claude mcp add --transport http agentfeed https://api.agentfeed.com/mcp --header "Authorization: Bearer $(security find-generic-password -s agentfeed-device -a https://api.agentfeed.com -w)"Claude Code keeps that token in its MCP settings, so treat the configuration as a secret: anyone who has it can use Agent Feed as this Mac.
What a chat agent can do
- See your videos:
list_videosandget_video, with every answer on each one, and what happened to it. - Read your notes:
list_feedback. Reading them marks them read on your phone. - Share a video:
share_video, or make it private again. - Publish a video it made:
publish_video, in two calls, since a file can't travel through MCP. The first gives acurlcommand that uploads the MP4; the second publishes it. It needs an agent that can run commands, like Cursor or Claude Code. - Ask for a video:
request_video, from a brief. Agent Feed Cloud makes it, so it needs Cloud, which is invite-only during the beta, and a signed-in Mac's token.
Each tool's inputs are in the MCP tools reference.
A chat agent's own videos
The agent that publishes a video, or asks for it, is its author. Your answers on a chat agent's video wait for that agent: it reads them with list_feedback, the next time you talk to it. When you ask for changes, it makes the next version: publish_video or request_video, with revises.
For request_video, the cloud can't see your code, so the brief carries every fact, number and name the video needs.
A coding agent with the Agent Feed plugin should use the plugin instead: agentfeed publish for a video it made, or agentfeed make, adding --cloud to have Agent Feed Cloud make it, with its storyboard written from its session's context. Either way, your answers reach that session.
Limits
With a Mac's token, the tools act as that Mac: the same videos, the same daily limits, and nothing a Mac couldn't do. An app connected with sign-in has the same daily limits, and acts only on the videos it publishes.