Attentive MCP server for your AI

No OAuth. You create a custom app in Attentive, and it shows the API key on a single screen; you paste that value into the API Key field on the connect form. PopMCP sends it server-side over HTTPS as an Authorization: Bearer header, so there is no redirect URL to register and no token refresh to babysit.

Yes. An Attentive API key is scoped to a single company, so the MCP server is locked to whichever company issued the key you pasted. Anything outside that company is simply not reachable through the connection.

It can do both, and you decide which. Writes include subscribe_user and unsubscribe_user, create_or_update_user for a full record in one call, post_custom_attributes for property data, and identify_user to attach a clientUserId so external ids work in place of phone or email later. CCPA deletion requests are available too, which is exactly the kind of write worth putting behind approval or ruling out with read-only mode.

That is what post_custom_event is for — it ingests a custom event representing a user action and is the primary way to kick off a journey from your own data. For commerce specifically there are dedicated events: product_view_event for browse abandonment, add_to_cart_event for cart abandonment, and purchase_event for post-purchase flows. Recording a purchase also suppresses the abandonment flows, so order your calls accordingly.

bulk_user_attributes creates or updates up to 256 users per async request. Because it is asynchronous, the call returns a job rather than finished work — poll get_bulk_job to see whether the ingestion succeeded. For a single record, create_or_update_user handles attributes, subscriptions and identifiers together in one call.

The segment tools work on API-managed segments, and each one is addressed by the externalId you assign at creation, not by its name. get_segment, update_segment, delete_segment and bulk_segment_members all key off that id, so losing track of it is the usual stumbling block. Use list_segments first — it filters by name or externalId and by last-updated time — and let the agent resolve the id before it writes.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 31 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 17-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 31 here. A trigger is something PopMCP watches for you: 12 Attentive events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Attentive.