Intuizi MCP Connector

What you need

An Intuizi account

Accounts are provisioned for customers under contract at console.intuizi.com. The connector is scoped to your account: the same projects, datasets, and data you can open in the console.

Your datasets enabled

POI, Apps, Web, CTV, Transactions, Demographics, Profile Attributes, Deidentified, and Origin are enabled per organization, so the catalogs you can reach follow your contract.

A destination, to activate

Activating an audience delivers it to a destination your team has configured in the Intuizi console. The connector delivers to destinations but cannot create them.

Connect your assistant

You never need to paste an API key. Simply point your assistant to the server URL, and it will direct you to console.intuizi.com to sign in and approve access.

Claude (web, desktop, and mobile)

Open Settings, then Connectors, and add Intuizi from the directory. If it is not listed yet, choose Add custom connector and paste https://console.intuizi.com/api/v2/mcp.
Click Connect. Claude sends you to console.intuizi.com.
Sign in with your Intuizi account and approve access. You are returned to Claude, ready to use.

Claude Code

Install the official Intuizi plugin

In Claude Code, run:

/plugin marketplace add intuizi/intuizi-claude-plugin
/plugin install intuizi@intuizi

Then run /mcp, choose intuizi, and approve access in your browser. See the official plugin repository.

Or connect the MCP server directly

claude mcp add --transport http intuizi https://console.intuizi.com/api/v2/mcp

Then run /mcp, choose intuizi, and authenticate in your browser.

ChatGPT

Find Intuizi in the plugin directory and click Connect.
Sign in to console.intuizi.com and approve access.

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth can use the same URL. For headless or unattended agents that cannot open a browser, create a dedicated MCP token on the My Account > MCP Tokens page in the Intuizi console and send it as a bearer token. The same page revokes it.

How a session flows

Building an audience is asynchronous. The creation call returns immediately while processing continues in the background, so your assistant will periodically check status until the build completes. A typical session follows four key steps:

Look up what you are targeting. Reference catalogs map human-readable names to specific ids (such as brands, POI categories, apps, CTV channels, merchants, or countries).
Size it before you build it. Running an estimate executes the same pipeline as a full build to return an estimated device count without creating an audience resource. Use this to compare targeting criteria before committing.
Build the audience. The assistant initiates audience creation and polls until the status updates to Completed (typically taking a few minutes for smaller audiences).
Preview, then activate. Previews show the exact number of retained devices across specified frequency thresholds. Once confirmed, activation delivers the audience to your configured target destination.

Estimates create no persistent assets, and previews initiate no data delivery. Because audience builds and activations draw from your organization’s metered data-scan allowance, your assistant should confirm with you before executing these actions.

Authentication and permissions

OAuth 2.1 with PKCE. You approve access in your browser. No password or API key is pasted into the assistant.
Your own permissions apply. Every call runs as you, with the same company scoping, dataset entitlements, and permissions as the Intuizi console and API. The connector cannot reach another company’s data.
Short-lived access tokens. Access tokens remain valid for approximately one hour, and your assistant refreshes them automatically in the background.
Revoke at any time. Disconnect the connector in your assistant, or revoke tokens on My Account > MCP Tokens in the console. Changing your console password invalidates every connector token immediately.
Safety labels. Every tool is explicitly labeled as either read-only or state-modifying. AI assistants execute read-only queries automatically and prompt for user confirmation before executing actions that create or delete resources.

Tool reference

The connector exposes 28 tools, each mapping directly to a single documented Intuizi API v2 endpoint. Consequently, validation rules, permissions, error responses, and rate limits mirror standard API behavior exactly.

Read and explore Read-only

Tool	What it does
`lookup_reference`	Reference catalogs: POI categories and brands, apps, web domains, CTV channels, Transactions merchants, demographic and profile attributes, countries, and signal providers.
`list_projects`	The projects in your account.
`list_audiences`	Your audiences, with search and pagination.
`get_audience`	One audience with its status, size, eligibility, and what it was built from.
`estimate_audience_size`	Starts a size estimate for an audience you have not built. Creates nothing.
`get_audience_estimate`	The result of an estimate: device count, coverage, and the date window behind it.
`list_cohorts`	Your cohorts, with search and pagination.
`get_cohort`	One cohort with its processing status and where it came from.
`preview_cohort_file`	Reads the first rows of your file so you can confirm the identifier column before creating a cohort.
`list_activations`	Your activations, with search and pagination.
`get_activation`	One activation with its delivery status.
`preview_activation`	Exactly how many devices a frequency range keeps, with the histogram and bounds. Nothing is created or billed.
`browse_poi_data`	Your POI segments, categories, brands, locations, and submissions.
`get_usage`	Your organization’s data-scan usage against its limit.

Create and deliver Write

Tool	What it does
`create_audience`	Builds an audience from POI visits, app usage, web domains, CTV viewing, Transactions, demographics, profile attributes, home location, or your own cohorts, alone or combined with AND, OR, and NOT IN.
`create_lookalike_audience`	Trains a lookalike model from a completed audience to reach a similar, larger group.
`create_activation`	Delivers a completed audience to a destination configured in the Intuizi console.
`create_cohort`	Creates a cohort from a cloud-hosted file, an uploaded file, or an existing audience.
`create_upload`	Reserves a secure upload slot so you can bring your own file in.
`create_project`	Creates a project to organize your work.
`create_poi_category`	Adds a POI category of your own.
`create_poi_brand`	Adds a POI brand of your own.
`create_poi_submission`	Submits locations for inclusion as points of interest.

Remove and cancel Destructive

Assistants always ask you to confirm these.

Tool	What it does
`delete_audience`	Permanently deletes one of your audiences.
`delete_activation`	Permanently deletes one of your activations.
`delete_cohort`	Permanently deletes one of your cohorts.
`delete_poi_submission`	Permanently deletes one of your POI submissions.
`cancel_lookalike`	Stops a lookalike model run that is still in progress.

Built-in documentation

The server publishes 20 read-only reference documents that assistants can inspect on demand: a getting-started guide, the tool reference, the API reference for each dataset, and the concepts behind responses, asynchronous work, errors, and idempotency. The assistant consults these resources whenever a request shape needs confirming, so you do not have to explain the API.

Limits and behavior

Topic	Behavior
Rate limits	120 reads and 30 writes per minute for each connection. If you go over, the error says how long to wait and your assistant retries.
Long-running work	Audiences, estimates, lookalike models, and activations run in the background. Your assistant polls until each one completes and reports failures with the reason.
Data-scan allowance	Each organization has a metered allowance that audience builds count against. Check it any time with `get_usage`. A build is refused once the limit is reached.
Repeated requests	Creates accept an idempotency key, so a retried request cannot quietly create the same audience or activation twice.
Availability	The connector runs on the same production platform as the Intuizi console and API v2.

Data and privacy

De-identified by design. The Large Behavioral Model identifies patterns, cohorts, affinities, places, context, and behavioral signals, not people. Intuizi does not attempt to re-identify anyone.
No audience data in the chat. Tool responses carry names, ids, statuses, counts, and settings. A finished audience is delivered only to the destination your team configured.
Your data stays yours. The connector reads and writes only your organization’s own resources, through the same API the console uses.
Nothing else is read. The connector sees only the arguments your assistant sends to a tool. Your conversations, your assistant’s memory, and your files never reach it.
Auditable. Everything the connector does appears in the Intuizi console, attributed to your account, exactly as if you had done it there.

For details, see the Privacy Policy, the Terms, and our Trust Center.

Example prompts

Explore“Which POI categories cover coffee shops, and which brands are in them?”

Size“How many people visited home improvement stores in Texas in the last 30 days?”

Build“Build an audience of coffee shop visitors in California over the last 30 days and tell me when it’s ready.”

Expand“Grow my Coffee Lovers audience with a lookalike.”

Activate“Preview my latest audience at frequency 3 to 10, then activate it to our S3 destination.”

Track“Which of my activations are still running, and how much of our data-scan allowance have we used this month?”

Troubleshooting

The connector says it is not authorized

Your session has expired or access was revoked. Remove the connector from your assistant and add it again, signing in to console.intuizi.com when asked. Changing your console password revokes every connector token by design.

A dataset or catalog I expect is missing

Datasets are enabled per organization, so what you can reach follows your contract. Ask your Intuizi contact or support@intuizi.com to enable one.

An audience stays unfinished

Builds are asynchronous, and a large one takes longer. Your assistant polls until it completes. If it fails, the status carries the reason. Ask for the audience’s status by name or id at any time, or open it in the Intuizi console.

I hit a rate limit

Each connection allows 120 reads and 30 writes per minute. The error says how long to wait, and your assistant retries after that.

My build was refused because of usage

Your organization reached its data-scan allowance. Ask for get_usage to see where you stand, then contact your Intuizi representative to raise the limit.

I cannot activate an audience

An activation needs two things: the audience must be completed, and a delivery destination must already be configured in the Intuizi console. The connector delivers to destinations but cannot create them.

Support

Email support@intuizi.com for help with the connector or your account, or privacy@intuizi.com for privacy questions. Customers can read the full API and MCP reference at console.intuizi.com/developers/mcp/ after signing in.

Intuizi, Inc. · 819 Reddick Street, 2nd Floor, Santa Barbara, CA 93103, United States