# MCP availability and integration requirements


MCP is an interface by which an agent client discovers and calls tools supplied by a server. This documentation does not publish a general-purpose Humanbased MCP server address or a universal tool-name contract. Do not paste a guessed endpoint into an agent client. If your organization supplies an integration, obtain its server address, tool inventory, authentication instructions, and data-handling terms from its administrator.

## Match a tool to an authorized task

For a first read, prefer one tool that takes a Subscription ID and a bounded page size and returns the HTTP data API's status, item count, and pagination state. The integration should use an organization credential held by its runtime, not a Key embedded in the agent's prompt. Its tool description should make the permitted environment and read mode explicit.

Before invoking it, confirm:

| Check | Why it matters |
| --- | --- |
| Server and environment | Production and staging credentials cannot be interchanged |
| Tool name and input schema | MCP tool names belong to the installed integration; they are not the HTTP paths |
| Organization and subscription scope | Discovery of a tool does not grant data access |
| Data destination | Retrieved records may be subject to terms that restrict sharing with the agent provider |
| Completion signal | A successful tool call is not proof that any record was returned or that all pages were read |

Use [the bounded agent task](/api/agent-access) as a template for what to ask the agent to do and report. The same server-side authorization and [data-use terms](/data/rights) apply whether the caller is a person, a script, or an MCP tool.

## If no MCP integration is supplied

Use the [documented HTTP data API](/api/api-data) from an approved runtime. For Campaign authoring, use the [Campaign API](/api/campaign-api) or a supported [CLI build](/api/cli) only with the relevant organization grant. These are usable interfaces on their own; MCP is an optional adapter, not a prerequisite.

An MCP server should not turn a person's browser session into a shared machine credential or silently confirm an agreement, launch, purchase, or payment. Those actions follow the product's own authorization and human-review rules. If an integration returns an unfamiliar response, stop and inspect its documented contract rather than inferring success from the tool invocation alone.