Skip to main content
Not connectedProduct

ChatGPT integration

Not directly available yet — here is the honest reason.

ChatGPT's MCP integrations authenticate external servers with OAuth. TexoAI's developer surface currently uses project-scoped bearer tokens, so a direct ChatGPT connection is not available yet. The same six tools are already usable from Codex, Claude Code, Cursor, n8n and your own API calls.

Connection methods

Not available yet

Setup

  1. Use another client today
    Codex, Claude Code, Cursor and n8n can connect to the same MCP endpoint or API with a project token right now.
  2. Create a token
    When you switch to a supported client, create a project token in Developer settings and copy the one-time mad_ value.
  3. Watch the roadmap
    OAuth-based MCP support for ChatGPT is planned; the roadmap page tracks it.

Available tools

ads.search
Read
ads:read
ads.get
Read
ads:read
ads.live_search_start
Write
ads:live
ads.live_search_get
Read
ads:read
boards.list
Read
boards:read
monitors.list
Read
monitors:read
jobs.get
Read
jobs:read
clones.submit
Write
Approved draft-only static job; never publishes to an ad account.

Common errors

Failures come back as HTTP 400 with a JSON-RPC error object (code + message), not as HTTP 401/403/429.

-32001 — invalid or missing token
tools/call requires a valid Authorization: Bearer mad_... header. Missing and invalid tokens both return JSON-RPC -32001 (HTTP 400). initialize, notifications/initialized and tools/list do not need a token.
-32003 — insufficient scope
The token is valid but lacks the scope the tool requires. Returned as JSON-RPC -32003 (HTTP 400). Change the token scopes in Developer settings, or call a read-only tool.
-32003 — rate limit exceeded
The token's one-minute window is exhausted. Returned as the same JSON-RPC -32003 (HTTP 400). Wait for the reset or raise the rate limit in Developer settings.
-32603 — tool failed
The tool call failed on the server. The HTTP status is still 400; check the JSON-RPC id and message for details.

FAQ