Connect an AI agent

Remote MCP server

https://api.benjiads.com/mcp

Use a client that supports remote MCP over Streamable HTTP. The endpoint supports legacy stateless clients and the 2026-07-28 request protocol. Configure the URL in the client's integrations or MCP settings, then sign in when prompted.

Clients with custom authorization headers can use a personal API key:

{
  "url": "https://api.benjiads.com/mcp",
  "headers": {
    "Authorization": "Bearer <your-api-key>"
  }
}

This is the connection information; the enclosing configuration format depends on your client. OAuth clients should discover the authorization server from the WWW-Authenticate challenge.

Discover, then act

Start with read permissions. For example:

Read my workspace, identify its vertical and state requirements, then show my site and this week's advertising results.

The server lists the tools allowed by the connection's scopes. The API reference gives each REST operation's matching MCP tool name.

Useful discovery tools:

• get_workspace: identify the connected business.
• list_verticals and get_vertical: discover supported trades and their rules.
• get_workspace_requirements: inspect location-specific license blockers.
• get_subscription: inspect the workspace subscription.
• list_campaigns: read campaigns and the available advertising balance.

Writes and user authorization

Before publishing a site or spending on advertising, agree on the intended change and budget with the user. Each write requires an idempotency_key. Reuse that key when retrying the same action.

Example arguments for publish_site:

{
  "idempotency_key": "publish-reviewed-homepage-001"
}

create_campaign prepares with launch disabled. Poll get_job and inspect the saved campaign before calling launch_campaign. A site, license, subscription, or funding restriction cannot be bypassed by the agent.

Subscriptions and owner handoffs

start_subscription returns a browser URL. The owner signs in and authorizes the recurring subscription in BenjiAds. The MCP call itself does not charge a card or activate access.

License verification, ad-wallet funding, and account permissions use the workspace dashboard. Agents must not collect card data or fabricate a license verification result.

Muse and other directories

The MCP endpoint is a general integration. Availability in Muse depends on the platform's connector contract and review. BenjiAds does not currently claim an approved Muse listing or a recurring subscription paid entirely inside a Muse/Link conversation.