About the Amperity MCP server

The Amperity MCP server enables AI assistants and agents to operate Amperity programmatically by using the Model Context Protocol (MCP). Connect any MCP-compatible client, such as Copilot Studio, Claude, or ChatGPT, to your Amperity tenant, and then use natural language to inspect data, run identity resolution, build queries and segments, create activations, run campaigns and journeys, and build predictive models.

The MCP server is hosted by Amperity. Customers connect to a single public endpoint and authenticate to the MCP server by using their existing Amperity credentials. The MCP server is not installed or run locally.

Private beta

The MCP server is available as a private beta. Tool surface, configuration, and behavior may change as the beta progresses. Tool count is approximate during beta and subject to change. Contact your Amperity representative for access.

MCP server URL

The Amperity MCP server is available at https://mcp.amperity.com. This URL automatically routes each request to the Amperity stack that hosts the calling user’s tenant. Use this URL in every place that the setup pages below reference an MCP host.

What is enabled?

The MCP server enables:

  • Conversational access to Amperity from Copilot Studio, Claude, ChatGPT, and other MCP-compatible clients.

  • More than 200 tools across tenants, such as databases, queries, identity resolution, campaigns, and predictive modeling. This full toolset is the default for connected clients.

    Note

    Copilot Studio limits the number of individual tools an agent can register. For Copilot Studio connections, the Amperity MCP server automatically serves a curated subset of tools that fits within this limit. See Tool surface limits.

  • Per-user isolation. Each request is authenticated and scoped to the calling user’s identity, tenant, and permissions.

  • Configurable safety modes for write operations.

What is not enabled?

The Amperity MCP server does not:

  • Bypass authorization to Amperity services.

    Important

    A user of the Amperity MCP server sees only the tenants and operations allowed by their credentials.

  • Store conversation history. Per-token session state–selected tenant and safety mode–persists across requests within the same session.

  • Control the AI client or its underlying model.

    Important

    Tool results may include personally identifiable information (PII). You are responsible for ensuring that the client and model you connect are approved to handle this data under your organization’s policies and any agreements with the model provider.

  • Replace the Amperity REST API.

    Important

    Use the Amperity API for programmatic integrations that do not involve an AI agent.

Connect a client

Connect a client to the MCP server: