Connect your own agent to Syndcast
Syndcast
Your own AI agent can work in your Syndcast channel, next to you. It comes in through one of three doors: MCP, the command line or the API. All three reach the same operations, with the same limits and the same credits behind them. This post shows each one, step by step.
First, a token
Every door starts with a token you make in your channel. You need to own the channel: only the owner can manage agent tokens.
- Open your channel and press Channel Settings.
- Open the Agents tab. The Agent Access card lists your tokens.
- Press New Token.
- Give it a Token name that says where you use it, such as "Claude Code on my laptop".
- Choose a Role: Editor, Viewer or Owner. The agent gets that role's access.
- Choose its Autonomy: Assist, Standard or Autopilot. The dialog says what each one allows. On Autopilot, set a Credit budget.
- If you like, pin it to one project with Project scope, or to one piece of content with Content scope.
- Press Create, then copy the token. It is never shown again.
A token works for one year.
MCP, for agent clients
MCP is the door for agent clients such as Claude Code and Cursor. After you create the token, the dialog shows the MCP endpoint and two tabs. On the Claude Code tab, copy the command and run it in the folder you work in. It looks like this:
claude mcp add --transport http syndcast https://syndcast.com/api/agent/mcp --header "Authorization: Bearer <your token>"
For another client, open the Other MCP clients tab and paste the config into your client's MCP config file.
To check that it works, ask your agent to list the projects in your channel. It answers with the projects on your channel's Projects tab.
The command line, for terminals and scripts
The syndcast command runs the same operations. Each one is a command: syndcast <family> <verb> --flags. It needs Node 20 or newer. There is no public package yet. During the beta, the Syndcast team sends it to you as a file. Install it like this:
npm i -g ./syndcast-<version>.tgz
Then sign in from your browser:
syndcast login --host https://syndcast.com
The terminal prints a link and a code. Open the link, check that the code on the page is the same, choose the Channel and what the command line may do, and press Approve.
syndcast ops lists every operation, and syndcast <family> <verb> --help shows the flags for one. Add --json in a script. The exit code tells the script what happened: 0 it worked, 3 it was not allowed, 4 it needs your approval, 5 it ran out of credits or was rate limited.
A CI job needs no browser. Set SYNDCAST_TOKEN to an agent token and SYNDCAST_HOST to https://syndcast.com.
The API, for your own code
Every operation is one HTTP request: a POST to /api/agent/v1/<family>/<verb>, with the token as a bearer token and the inputs as a JSON body.
curl -X POST https://syndcast.com/api/agent/v1/access/me -H "Authorization: Bearer <your token>" -H "Content-Type: application/json" -d '{}'
Every operation, with its inputs and answers, is listed at https://syndcast.com/api/agent/v1/openapi.json.
When your agent needs a yes
Some requests need you. They wait in your channel's Agent tab, where you approve or decline them. Through MCP and the command line, the agent waits and picks up your answer within seconds. The API does not wait: it answers approval_required, and your code reads the open request with confirmations.list and sends the same request again after you answer.
You see your agent's work in the app as it happens.
Hand work to Syndcast's agents
With the Owner or Editor role, your agent can brief Syndcast's own agents, and they do the work inside your channel. It can also make helper tokens for other agents. A helper never has more access than the token that made it, and lasts 24 hours at most.
Cut it off
Each token in Active tokens shows its role and scope. To cut one off, press its revoke button, then Revoke Token. This cannot be undone, and it revokes the token's helpers too. Tasks it gave Syndcast's agents keep running until you stop them in the Agent tab.
Try it
Syndcast is in private beta. If you want to connect your agent, join the waitlist. The full steps are in the docs, under Connect your agent.