Before you start
- A Bidhelm workspace with a plan. Agents work on every plan, at no extra cost.
- An agent that supports remote MCP servers: Claude Code, Codex, Claude on the web and desktop, or another MCP client.
The server address
It is the same for everyone. Your login decides which workspaces the agent sees.
Add Bidhelm to your agent
Add the server from your terminal:
Terminal$ claude mcp add --transport http bidhelm https://mcp.bidhelm.com/mcp- Start Claude Code and run
/mcp. Pick bidhelm, then Authenticate. - Your browser opens the Bidhelm sign-in. Sign in and select Allow.
Add --scope user to the command to use Bidhelm in every project, not only the one you are in.
Add the server from your terminal:
Terminal$ codex mcp add bidhelm --url https://mcp.bidhelm.com/mcpSign in:
Terminal$ codex mcp login bidhelm- Your browser opens the Bidhelm sign-in. Sign in and select Allow.
- In Claude, open Customize âș Connectors, select + Add, then Add custom connector.
- Name it Bidhelm, paste the server address and select Add.
- Select Connect, sign in to Bidhelm and select Allow.
On Team and Enterprise plans, an owner adds the connector first under Organization settings âș Connectors. Then each person connects with their own Bidhelm login.
- In your client's settings, add a remote MCP server with the server address. The transport is Streamable HTTP.
- When the client asks you to sign in, use your Bidhelm login and select Allow.
Bidhelm signs in clients that identify themselves with a client ID metadata document, as the current MCP spec describes. A client that only supports dynamic client registration can't connect yet.
Sign in and allow
The first time your agent connects, it opens a Bidhelm page in your browser. Sign in with your Bidhelm login and select Allow. Your agent then works as you: it sees the workspaces you belong to and can do what your role allows. It stays connected, so you sign in once.
Try it
Ask in plain words. Your agent picks the right Bidhelm tool.
- âWhat changed in my account this week, and why?âget_recent_activity
- âIs anything waiting on me?âget_needs_you
- âPause any campaign that spent over $200 this week without a trial.ârequest_action
- âPlan next weekâs posts around the launch.ârequest_action
What your agent can do
Anything you can do in the dashboard, apart from a few account tasks. The full list is in What your agent can do.
| Area | What it can do |
|---|---|
| Ads | Read campaigns and results, pause and resume, change budgets and bids, add and remove keywords, review ad drafts. |
| Social | Read and edit the queue, approve and reschedule posts, change settings, answer conversations. |
| Landing pages | See every page and the leads it brought, rebuild a page or change where it sends people. |
| Reports | Read past reports and start a new one. |
| History and Memory | Read every change and the reason for it, and edit what Bidhelm has learned. |
| Plan and settings | Read and change the monthly ad budget, permissions and business profile. |
| Dashboard only | Payments, your Bidhelm subscription and invoices. Members, invites and roles. Connecting or disconnecting accounts. Uploading images. The workspaceâs address and logo. |
Changes that ask you first
Some changes spend money, publish under your name or can't be undone, such as approving an ad draft, approving a post or raising the monthly budget. Bidhelm tells your agent to ask you before it makes them, and the ones that can't be undone are refused until your agent confirms. The full list is in What your agent can do.
Every change your agent makes is recorded in History as made by You, marked via your agent.
Disconnect
Remove Bidhelm where you added it. Your account and its History stay as they are.
$ claude mcp remove bidhelm$ codex mcp remove bidhelmIn Claude, open Customize âș Connectors, open Bidhelm and remove it.
Troubleshooting
In Claude Code, run /mcp, pick bidhelm and choose Authenticate again. In Codex, run codex mcp login bidhelm.
Agents need a workspace with a plan. Finish setup at app.bidhelm.com, then ask again.
Bidhelm signs in clients that identify themselves with a client ID metadata document. A client that only supports dynamic client registration canât connect yet.
More fixes are in Troubleshooting agents.