Connect Anteriad to Claude: Monitor Intent Topics and Audience Size

If you need to connect Anteriad to Claude to automate B2B intent monitoring, account matching, or audience size analysis, you need a Model Context Protocol (MCP) server. This server acts as the translation layer between Claude's tool calls and Anteriad's REST APIs. You can either build and maintain this infrastructure yourself, or use a managed integration platform like Truto to dynamically generate a secure, authenticated MCP server URL. If your team uses ChatGPT, check out our guide on connecting Anteriad to ChatGPT or explore our broader architectural overview on connecting Anteriad to AI Agents.

Giving a Large Language Model (LLM) read access to a massive B2B intent database like Anteriad is an engineering challenge. You have to handle fragmented identity resolution mechanisms, map massive JSON schemas to MCP tool definitions, and deal with upstream rate limits gracefully. Every time Anteriad updates an endpoint or deprecates an intent topic structure, you have to update your server code, redeploy, and test the integration. This guide breaks down exactly how to use Truto to generate a secure, managed MCP server for Anteriad, connect it natively to Claude, and execute complex audience workflows using natural language.

The Engineering Reality of the Anteriad API

A custom MCP server is a self-hosted integration layer. While the open MCP standard provides a predictable way for models to discover tools, the reality of implementing it against Anteriad's APIs requires significant domain knowledge. You are not just integrating a simple CRM - you are querying complex B2B identity graphs and high-volume intent signals.

If you decide to build a custom MCP server for Anteriad, you own the entire API lifecycle. Here are the specific challenges you will face:

Fragmented Identity Resolution Querying intent data in Anteriad is rarely a single API call. If a user asks Claude, "What intent topics is Acme Corp researching?", the agent cannot simply query an Acme Corp string. It must first resolve the company via the match endpoint or find an account_link using a domain, IP address, or CIDR block. Once the agent retrieves the account_link_id, it must pass that specific ID to the intent or Xplorer contact endpoints. If your MCP server does not expose these endpoints with explicitly linked descriptions, the LLM will hallucinate IDs or attempt invalid operations. Truto derives tool definitions dynamically from the integration's documentation schemas, ensuring Claude knows exactly how to chain these resolution requests.

Strict Filter Formats and Thresholds Anteriad intent APIs rely on specific score thresholds and content-type filters to separate weak signals from actionable buying intent. The schemas dictate exactly how these filters must be formatted. Writing custom JSON schemas for Claude to understand score vs threshold parameters is tedious. A managed MCP server parses Anteriad's native schemas and automatically translates them into strict JSON Schema formats the LLM natively understands.

Rate Limit Passthrough and Backoff Requirements When you build AI agents that iterate over hundreds of account links to aggregate intent topics, you will hit Anteriad's API rate limits. It is a common misconception that middleware should swallow these errors. Truto does not retry, throttle, or apply backoff on rate limit errors. When the upstream Anteriad API returns an HTTP 429 Too Many Requests, Truto passes that error directly back to the caller. Crucially, Truto normalizes the upstream rate limit information into standardized headers (ratelimit-limit, ratelimit-remaining, ratelimit-reset) per the IETF specification. This explicit passthrough guarantees that your AI agent framework (whether LangGraph, CrewAI, or Claude Desktop) receives the exact state of the rate limit and can execute its own intelligent backoff strategy.

Instead of building this infrastructure from scratch, you can generate an Anteriad MCP server in minutes. Truto normalizes authentication, pagination, and tool generation dynamically.

How to Generate an Anteriad MCP Server with Truto

Truto creates MCP servers dynamically based on the integrated account's configuration. The tool generation is documentation-driven, meaning tools are generated entirely from Anteriad's config.resources and documentation records.

You can create this server in two ways.

Method 1: Via the Truto UI

For administrators setting up internal agents, the UI provides a fast, no-code path:

1. Navigate to the Anteriad integrated account page within your Truto dashboard.
2. Click the MCP Servers tab.
3. Click Create MCP Server.
4. Configure your desired permissions (e.g., restricting to read-only methods or specific tool tags like intent or audience).
5. Copy the generated MCP server URL. (You will never see this raw token again, as it is hashed before being stored in Truto's KV infrastructure).

Method 2: Via the API

For engineers embedding AI capabilities into their own SaaS platforms, you can programmatically provision MCP servers for your end-users. The API validates that the Anteriad integration is AI-ready, generates a secure token, and returns the URL.

// POST /integrated-account/:id/mcp
const response = await fetch('https://api.truto.one/integrated-account/YOUR_ANTERIAD_ACCOUNT_ID/mcp', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_TRUTO_API_TOKEN',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    name: "Anteriad Intent Agent Server",
    config: {
      methods: ["read"],
      tags: ["intent", "xplorer"]
    },
    expires_at: "2026-12-31T23:59:59Z"
  })
});
 
const mcpServer = await response.json();
console.log(mcpServer.url); 
// Returns: https://api.truto.one/mcp/a1b2c3d4e5f6...

How to Connect the MCP Server to Claude

Once you have the Truto MCP server URL, connecting it to Claude is a matter of configuration. The MCP server is fully self-contained - the URL contains the cryptographic token necessary to authenticate requests against that specific Anteriad instance.

Method A: Via the Claude UI

If you are using Claude's web interface or supported desktop integrations that provide a UI for Custom Connectors:

1. Open Claude and navigate to Settings.
2. Click on Integrations (or Connectors depending on your tier).
3. Select Add MCP Server or Add Custom Connector.
4. Paste the Truto MCP server URL and click Add.
5. Claude will immediately handshake with the server (via the initialize JSON-RPC method) and fetch the available Anteriad tools.

Method B: Via Manual Config File

For Claude Desktop users running custom agent frameworks locally, you configure the server using your claude_desktop_config.json file. Because Truto's MCP servers communicate over HTTP Server-Sent Events (SSE), you use the official @modelcontextprotocol/server-sse transport wrapper.

{
  "mcpServers": {
    "anteriad_intent": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sse",
        "https://api.truto.one/mcp/YOUR_TRUTO_MCP_TOKEN"
      ]
    }
  }
}

Restart Claude Desktop. The agent will read the config, initialize the SSE connection, and populate the tool context with Anteriad endpoints.

Security and Access Control

Giving an LLM access to your enterprise data requires strict governance. Truto enforces security at the MCP token level, allowing you to tightly scope what the LLM can do.

• Method Filtering: Limit the server to specific HTTP methods. Passing methods: ["read"] ensures the agent can only execute get and list operations, preventing it from accidentally writing or deleting data.
• Tag Filtering: Group tools by functional area. By passing tags: ["intent"], the agent will only see tools related to intent monitoring, hiding Xplorer or MAID tools.
• Require API Token Auth: By setting require_api_token_auth: true, the bare MCP URL is no longer sufficient. The caller must also pass a valid Truto API token in the Authorization header, adding a secondary layer of authentication for highly sensitive environments.
• Expiration (TTL): Use the expires_at property to create ephemeral MCP servers. Truto uses distributed alarms to automatically clean up the database records and KV entries once the TTL passes, preventing stale tokens from accumulating.

Anteriad Hero Tools for AI Agents

Truto auto-generates tools directly from Anteriad's endpoint documentation. Here are the highest-leverage tools available to Claude for building intent workflows.

list_all_anteriad_account_link

This tool is the critical first step in Anteriad workflows. It searches the account linkage database to resolve domains, IPs, or CIDR blocks into a specific account_link_id. The LLM must use this tool to anchor its subsequent queries.

"I have a list of IP addresses that hit our pricing page today. Can you run them through Anteriad and get the associated account link IDs and domain names?"

list_all_anteriad_intent

Retrieves the detailed intent records for a specific company or topic. It requires a topic parameter and returns the intent attributes for the best-matched companies, allowing Claude to assess buyer readiness.

"Fetch the latest intent records for the topic 'Cloud Infrastructure Migration'. Filter for high score thresholds and summarize the top 5 companies showing the strongest buying signals."

list_all_anteriad_match

Resolves a company's raw name and address into a standardized Anteriad company record. This is essential when crossing CRM data (like Salesforce accounts) with Anteriad's dataset, as it handles fuzzy matching.

"Take these three companies from my pipeline: Acme Corp in New York, Globex in Austin, and Initech in Seattle. Use Anteriad to find their matched company records and return their standardized industry codes."

list_all_anteriad_intent_topics

Lists the best matched company records for an intent topic. This tool supports optional filters for threshold and score, allowing the agent to refine large datasets into actionable target lists.

"Find all companies showing intent for 'Zero Trust Security'. Apply a high intent score threshold, and create a markdown table of the results including their company names and primary domains."

list_all_anteriad_xplorer_contact_counts

Once an account link is identified, this tool queries the Anteriad Xplorer database to return contact counts for that account. It is highly useful for determining if a high-intent account actually has addressable contacts in your target persona.

"We found that account_link_id 98765 is showing high intent for our product. Query the Xplorer contact counts for this account to see how many IT Director level contacts are available for outreach."

For the complete tool inventory and granular JSON schema details, refer to the Anteriad integration page.

Workflows in Action

With the MCP server connected, Claude can orchestrate complex, multi-step Anteriad workflows autonomously. The agent uses the schema definitions to chain responses from one tool directly into the parameters of the next.

Workflow 1: Resolving a Domain and Auditing Intent

The Prompt:

"A visitor from techlogistics.com just downloaded our whitepaper. Find their Anteriad account link, then check what other intent topics they are actively researching. Summarize their overall buyer readiness."

The Execution:

1. Claude calls list_all_anteriad_account_link passing domain: "techlogistics.com".
2. Anteriad returns the account linkage data, including the core account_link_id.
3. Claude extracts the ID and calls list_all_anteriad_intent_counts to see the total volume of intent signals for that specific account link.
4. Claude then calls list_all_anteriad_intent using the matched company details to retrieve specific topics.
5. The agent synthesizes the raw intent scores into a readable briefing, noting that the company is heavily researching competitor products and supply chain optimization.

sequenceDiagram
    participant User
    participant Claude as Claude Agent
    participant Truto as Truto MCP
    participant Anteriad as Anteriad API

    User->>Claude: "Analyze intent for techlogistics.com"
    Claude->>Truto: call list_all_anteriad_account_link(domain: "techlogistics.com")
    Truto->>Anteriad: GET /account_links?domain=techlogistics.com
    Anteriad-->>Truto: { account_link_id: "acc_8842" }
    Truto-->>Claude: Return account link ID
    
    Claude->>Truto: call list_all_anteriad_intent(id: "acc_8842")
    Truto->>Anteriad: GET /intent?account_link_id=acc_8842
    Anteriad-->>Truto: [ { topic: "Logistics Software", score: 95 } ]
    Truto-->>Claude: Return intent data
    
    Claude-->>User: "TechLogistics is showing 95/100 intent for Logistics Software..."

Workflow 2: Building an Audience from a Target Topic

The Prompt:

"We are launching a new enterprise firewall. Find the top companies currently showing high intent for 'Network Security Hardware' with a score above 80. For the top 3 companies, check their Xplorer contact counts to ensure we have addressable leads."

The Execution:

1. Claude calls list_all_anteriad_intent_topics with topic: "Network Security Hardware" and score: 80.
2. Anteriad returns an array of matched companies hitting that threshold.
3. Claude extracts the accountLinkId for the top 3 results.
4. Claude iteratively calls list_all_anteriad_xplorer_contact_counts passing the respective account_link_id for each of the three companies.
5. The agent formats the response, presenting the top three companies, their intent score, and the exact number of discoverable contacts available in the Anteriad Xplorer database.

Stop Building Boilerplate

Building a custom integration to bridge Claude and Anteriad means wasting engineering cycles on schema mapping, token hashing, and error normalization. Anteriad's dataset is incredibly powerful, but its fragmented resolution endpoints require strict, predictable tooling for LLMs to use it effectively.

Truto abstracts this entire layer. By deriving MCP tools directly from integration documentation and passing rate limits explicitly to your frameworks via IETF standardized headers, you guarantee your agents have reliable, real-time access to intent data without maintaining thousands of lines of TypeScript.