Connect OpenClaw
Add UniFeeds to OpenClaw with one command, then sign in.
Before you start
- OpenClaw installed and up to date, with the Gateway running.
- OpenClaw is free and open source, so there's no plan to check.
- Always add UniFeeds with the streamable-http transport. Without it, OpenClaw uses an older connection type that UniFeeds doesn't support.
- At least one social account connected on the Connections page in UniFeeds, so the AI has somewhere to post.
Connect
Add UniFeeds
openclaw mcp add unifeeds --url https://mcp.unifeeds.io/mcp --transport streamable-http --auth oauthSign in
Run this and open the link it prints. Sign in to UniFeeds, pick your workspace, and click Allow. OpenClaw finishes on its own.
openclaw mcp login unifeedsCheck it works
The probe should connect and list UniFeeds' tools. A running Gateway can take up to 10 minutes to show them; openclaw mcp reload loads them now.
openclaw mcp doctor unifeeds --probeOther ways to set it up
In the Control UI
Sign in from the Control UI or from the terminal, not both. They use different sign-in addresses, so run openclaw mcp logout unifeeds before you switch.
Add a server
Open Settings, then MCP, and select Add server.
Enter UniFeeds' details
Name it unifeeds, choose Streamable HTTP, and paste this URL.
https://mcp.unifeeds.io/mcpTurn on sign-in
Set "auth": "oauth" in the server's config, save, then select Sign in on its row. This needs an OpenClaw admin connection. Open the Control UI at the Gateway's local address (http://127.0.0.1:<port>). Sign-in through a Tailscale or public address won't work; run openclaw mcp login unifeeds instead.
Edit openclaw.json yourself
Add this to ~/.openclaw/openclaw.json
Then run openclaw mcp login unifeeds.
{
mcp: {
servers: {
unifeeds: {
url: "https://mcp.unifeeds.io/mcp",
transport: "streamable-http",
auth: "oauth",
},
},
},
}Check it works
Start a new session and ask:
Use the UniFeeds whoami tool and tell me which workspace you're connected to and whether you can make changes.OpenClaw should name your UniFeeds workspace and say whether it can make changes. If it picked the wrong workspace or can only read, reconnect and choose again. With an API key, use a read and write key made in the right workspace.
Manage the connection
Sign out of UniFeeds and keep the server, or remove it from OpenClaw.
openclaw mcp logout unifeeds
openclaw mcp unset unifeedsTo cut the app off from UniFeeds' side, open Connected apps on the API keys page and select Disconnect. Workspace members can disconnect their own apps; admins can disconnect any.
Use an API key instead
If you'd rather not sign in.
Troubleshooting
OpenClaw hides a server until it's signed in. Run openclaw mcp login unifeeds, then openclaw mcp reload. Check with openclaw mcp doctor unifeeds --probe.
Check that the transport is streamable-http. Add UniFeeds again with the command above.
After you click Allow, the page won't load. Copy the code= value from its address bar and run openclaw mcp login unifeeds --code <code>.
Each one signs in with its own address. Run openclaw mcp logout unifeeds, then sign in again from the one you want to use.
Sign-in there needs an OpenClaw admin connection on the Gateway's local address. Run openclaw mcp login unifeeds in a terminal instead.
This happens when the AI needs access you didn't allow. Run openclaw mcp login unifeeds. Any workspace member can connect an AI app to read, but only workspace admins can let it make changes. If you're an admin, sign in again and tick the option to create, schedule, publish and delete posts.
Sign-in and workspace problems that happen in every app are on the Troubleshooting page. Still stuck? Email support@unifeeds.io.