Connect an AI client

Every client uses the same server URL, https://adrails.ai/api/mcp, and the same sign-in: the client registers itself, you sign in to Adrails, then choose the workspace and the permissions on the consent screen. What the screen asks is explained in Permissions.

The MCP page in Adrails gives these steps too, with the URL and the commands ready to copy.

ClaudeCopy Anchor Link

On claude.ai and in the Claude desktop app:

1. Open Settings, then Connectors, and choose Add custom connector.
2. Name it Adrails and paste https://adrails.ai/api/mcp as the server URL. Leave the optional OAuth client ID and client secret empty: Claude registers itself.
3. Add the connector, then connect it. Adrails opens: sign in, choose the workspace and the permissions, and choose Allow access.
4. Enable Adrails in a conversation and ask your first question.

On a Claude Team or Enterprise plan, an owner of your Claude organization may have to add the connector first.

When Claude asks you to allow a tool call, that is Claude's own setting. An advertising change still waits for your approval in Adrails.

Claude CodeCopy Anchor Link

Run, from your project directory:

claude mcp add --transport http adrails https://adrails.ai/api/mcp

Then, in Claude Code, run /mcp, select adrails and authenticate. Your browser opens Adrails for the sign-in and the consent screen; return to Claude Code once you have allowed access.

ChatGPTCopy Anchor Link

1. In ChatGPT Settings, turn on Developer mode. Whether you can depends on your ChatGPT plan and your workspace's policy.
2. Open Plugins and add a custom MCP server named Adrails, with https://adrails.ai/api/mcp as its URL and OAuth as its authentication.
3. Sign in to Adrails, choose the workspace and the permissions, and choose Allow access.
4. Review the tools ChatGPT discovered, then add Adrails to a new conversation.

CodexCopy Anchor Link

Run:

codex mcp add adrails --url https://adrails.ai/api/mcp
codex mcp login adrails --scopes adrails:read,offline_access,adrails:actions:prepare,adrails:integrations:manage,adrails:workflows:manage,adrails:knowledge:write,adrails:campaigns:write

The second command asks for every permission, so the consent screen offers them all. Only read access and Stay connected are selected at first: select the others you want, or remove them from --scopes so they are never offered.

Codex may ask you to allow a call that changes something, depending on its approval settings. Then start Codex and ask it to use the Adrails tools.

Another clientCopy Anchor Link

A client connects when it supports all of the following:

• Remote MCP over Streamable HTTP. Requests are POST; there is no event stream.
• OAuth with dynamic client registration. Adrails gives out no client ID: the client registers at the endpoint the discovery document names.
• Authorization code with PKCE, method S256, and the resource parameter set to https://adrails.ai/api/mcp.
• A callback Adrails accepts: an https address on a public host; an http address on localhost, 127.0.0.1 or [::1] for an app on your computer; or a private scheme written as a reverse domain name with no host, such as com.example.app:/callback. Registration refuses any other callback.

A client that runs in a web page on another site is refused unless Adrails allows that site. Desktop and command-line clients are not concerned.

In such a client, add a remote MCP server named Adrails with the server URL, choose Streamable HTTP and OAuth if it asks, and follow its sign-in link. The endpoints are listed in For client developers.

Check the connectionCopy Anchor Link

Ask your assistant:

• Which integrations are connected to my workspace?
• Compare campaign performance this week with last week.
• Prepare a daily budget increase for my best-performing campaign. With Prepare advertising changes, it returns a proposal and its approval link; nothing changes before you approve.

Your client now appears under Your connections on the MCP page in Adrails.

When it does not workCopy Anchor Link

• The client says it needs authentication. The connection was revoked, or it expired without Stay connected. Connect again.
• A write tool is missing. The connection lacks its permission, or the tool needs an owner or admin. Connect again and select the permission. If the consent screen never offers it, remove Adrails from your client and add it again, so the client asks for permissions afresh.
• The consent screen says the request expired or changed. Start again from your AI client.
• "Another call is running on this connection." The client sent two calls at once. Calls on one connection run one at a time; the second can simply be sent again.