Skip to main content
Back to home
LiveProduct

Integrations

Search, monitor and generate ads from the AI agents you already use.

TexoAI exposes a real JSON-RPC developer surface. Connect an MCP client or call the API directly with a project-scoped token. This page lists exactly what is available today and what is not — no fabricated install steps.

Delivery methods

MCPAvailable

A Model Context Protocol server at /api/developer/mcp. Point any MCP client at it with a project token. Available today.

Clients

Each page shows the real setup for that client and its current limitations.

Codex

MCP

Open page

Claude Code

MCP

Open page

Cursor

MCP

Open page

ChatGPT

Not available yet

Open page

n8n

API

Open page

API

API

Open page

What your agent can do

Six tools are exposed today. Five are read-only; one guarded write tool submits an approved, draft-only static clone job.

Read
ads.search
Search the ad library

Search canonical ads by brand, keyword or headline with the same filters and source disclosure as the product.

Read
ads.get
Read a single ad

Read the full creative fields of one canonical ad in the bound project.

Read
boards.list
List your boards

List the private Boards saved in the bound project.

Read
monitors.list
View your monitors

List the monitors in the bound project with their current state.

Read
jobs.get
Query a job

Read the status and result of a generation Job in the bound workspace.

Write
clones.submit
Submit a draft clone job

Create an internal draft job for static image or ad-analysis work. Requires approved: true and never publishes.

Permissions

Every call is checked against the token's scopes and the creator's current project membership.

Read-only by default
ads.search, ads.get, boards.list, monitors.list and jobs.get only read data inside the bound project. Nothing is mutated.
One guarded write tool
clones.submit requires the clones:submit scope and the explicit approved: true argument, and only creates an internal draft job for static image or ad-analysis work. It can never publish to an advertising account.
Reserved scopes
boards:write and monitors:write exist as scopes but grant no external mutation endpoint yet.

A real exchange

The endpoint is JSON-RPC 2.0 over HTTPS POST. Initialize, list tools, then call a tool with a Bearer token.

Request
POST /api/developer/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}
Response
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "tools": [
      { "name": "ads.search", "scope": "ads:read", "description": "Search canonical ads in the bound project." },
      { "name": "ads.get", "scope": "ads:read", "description": "Read a canonical ad in the bound project." },
      { "name": "boards.list", "scope": "boards:read", "description": "List private Boards in the bound project." },
      { "name": "monitors.list", "scope": "monitors:read", "description": "List monitors in the bound project." },
      { "name": "jobs.get", "scope": "jobs:read", "description": "Read a generation Job in the bound workspace." },
      { "name": "clones.submit", "scope": "clones:submit", "description": "Submit an approved, draft-only static clone Job." }
    ]
  }
}

Security

Credentials are project-scoped, stored as SHA-256 digests, and every call is rate-limited and audited.

One-time tokens
Tokens are prefixed mad_ and shown once at creation. Only a SHA-256 digest is stored. Revoke any token at any time.
Least-privilege scopes
Each token carries only the scopes you choose, from ads:read to clones:submit. Optional expiry is enforced on every call.
Audit log
Token creation, revocation, webhook changes and every external tool call are appended to the project audit log.
Rate limits
A fixed one-minute window per token (default 60 requests, up to 600). Limit, remaining and reset are returned as X-RateLimit-* headers.

Honest limitations

These pages describe only what is implemented today.

  1. No Skill or CLI package yet
    Skill instruction packages and a CLI binary are not shipped yet. Use the MCP server or the API instead.
  2. Webhooks are configured, not delivered
    You can register HTTPS webhook destinations and event allowlists, but no events are dispatched to them yet.
  3. No video, no publishing
    The developer surface never runs video work and never publishes to an advertising account.

Developer resources

Manage credentials in the product and follow what ships next.

Developer settings

Create project-scoped tokens, register webhooks and review audit history in-app.

Changelog

Track what ships on the developer surface.

Roadmap

See the planned Skill, CLI and webhook delivery work.

Create a token

Open Developer settings, pick a project, choose the scopes you need and copy the one-time token.

Open Developer settingsView pricing