Connect an AI agent (MCP)
draftConnect an AI agent to Binoban over MCP (Model Context Protocol), so it can read the developer documentation, check your events and help you build an integration in your own code.
The MCP server is new. Your deployment may not have it switched on yet. If a connection fails, ask your Binoban administrator.
Choose a connection
Binoban serves two MCP connections. Both run on your deployment's host, shown
here as <your-host>.
| Without sign-in | Signed in | |
|---|---|---|
| Address | https://<your-host>/api/mcp/public | https://<your-host>/api/mcp |
| Who it's for | Anyone building an integration, with or without a Binoban account | People with an account on the platform |
| Documentation and event tools | Yes | Yes |
| Your platform's data sources, keys, events and ad slots | No | Yes, within your own permissions |
Use the signed-in connection if you have an account: it does everything the other one does. Use the one without sign-in when you don't have an account yet, or when you're a developer working for a customer who manages the account.
Connect without signing in
- Add the server to your agent:
- Claude Code: run
claude mcp add --transport http binoban-docs https://<your-host>/api/mcp/public - Claude: open Settings → Connectors, choose Add custom connector and paste the address.
- ChatGPT: open Settings → Apps and connectors, create a connector, paste the address and choose no authentication. Custom connectors may need developer mode, which a workspace admin turns on.
- Claude Code: run
- Ask the agent what Binoban is, or ask it to integrate Binoban into your code.
Without sign-in the agent can't see your keys. It writes placeholders such as
<API_KEY> and tells you where in the Binoban panel to find each value.
Connect with your account
- Add
https://<your-host>/api/mcpthe same way as above. In Claude and ChatGPT, choose OAuth for authentication. - When the agent first connects, the Binoban panel opens in your browser. Sign in, pick the platform to connect, and tick what the agent may do. Read is always included; create, edit, delete, and launch and send are optional.
- Choose Allow.
The agent can then find the data source of your app's type, which holds the
sourceIdentifier and apiKey, and propose creating one if there is none.
Every change waits for you to confirm it in the chat. To revoke access, open
Management → AI apps in the panel and disconnect the app.
Run the guided integration
Both connections offer a prompt, integrate_binoban, that walks an agent
through an integration: install the SDK, identify users, map your app to
events, check every call, add ads if you want them, and finish with the
go-live checklist.
In Claude Code, type / and pick it under the server's name, for example
/mcp__binoban-docs__integrate_binoban. It takes two optional arguments:
| Argument | Values |
|---|---|
platform | web, android, ios, react-native or backend. Detected from your code when omitted. |
goal | tracking, push, ads, or several of them. |
What the agent can use
| Tool | What it does |
|---|---|
search_docs | Searches the Binoban developer documentation |
read_doc | Opens a documentation page, or one section of it |
list_standard_events | Lists the standard events: ecommerce (product_viewed, order_completed…), page, app lifecycle and notification events |
describe_event | Gives a standard event's properties and their types |
validate_event | Checks an identify or track payload before you ship it: identifiers, event and property names, reserved names, and the property types of standard events |
describe_tracking_api | Gives the exact contract of a tracking endpoint: track, identify, catalog, ad impression and click |
connect_account | Without sign-in only: how to switch to the signed-in connection |
Prefer standard events over custom ones: reports, funnels and ad conversion understand them. See the ecommerce events.
Limits
- On-prem and air-gapped deployments. The documentation tools read the public developer documentation. A deployment that can't reach it may return no search results, while the event tools keep working.
- Clients that only run local (stdio) servers can't connect directly. Both connections are remote servers over HTTP.
- The agent proves your code calls the SDK correctly, not that Binoban received the events. Check that with debug mode or the Inspector.