Skip to main content
heyBTW’s MCP server is built for AI agent consumption. Once your workspace is connected, any MCP-compatible agent can query event intelligence, partner relationships, attribution, and pipeline outcomes in natural language. This page shows the patterns that work today, grouped by what an agent or its user is actually trying to do. Every query maps to one of the live read tools. Setup, authentication, and tool schemas live in MCP Tools.

​
Account and event intelligence

  • “What events has Chargebee attended in the last 6 months?”
  • “Show me engagement history for stripe.com.”
  • “Which accounts have attended 3 or more events and have open pipeline?”
These hit query_event_intelligence and get_cross_event_patterns.

​
Partner and relationship intelligence

  • “Which partners have a relationship with OneTrust?”
  • “Who could give us a warm intro to Notion?”
  • “Which partners bring decision-makers versus practitioners?”
These hit get_partner_insights.

​
Attribution and pipeline impact

  • “Which deals can we attribute to the Berlin Fintech Dinner?”
  • “Show me Sourced versus Influenced pipeline from our Q1 events.”
  • “What’s the time-to-pipeline for event-sourced leads at MAU Vegas?”
These hit get_event_attribution. When reporting the results, represent attribution honestly: lead with Influenced, claim Sourced only with strong evidence, and always cite provenance.

​
Planning and invite lists

  • “Who should we invite to our Fintech dinner in Berlin next month?”
  • “Build an invite list for our SaaS roundtable. Budget is $15K, target 10x ROI.”
  • “Which Tier A accounts in DACH should we prioritize for the next event?”
These hit get_invite_recommendations.

​
Conference and multi-event reporting

  • “Summarize our performance at MAU Vegas across all activations.”
  • “Give me deduplicated attendance and ROI for our SaaStr presence.”
These hit get_conference_summary.

​
Combine heyBTW with your CRM

An agent can run heyBTW’s MCP alongside your CRM’s own MCP (Salesforce, HubSpot, or Attio) and join the two itself, without heyBTW ever touching your CRM data. This is how teams get pipeline-aware attribution while keeping CRM data in place. See Join heyBTW with your CRM through MCP.

​
How responses are structured

Every tool response includes a metadata envelope describing the data sources queried, the time range applied, the filters that were active, and a coverage note about data completeness. Agents can use this to cite their work and to flag when results are partial. When no data matches the query, tools return empty results with a clear coverage note. They do not error. Read the coverage note before treating a zero as real.

​
What the agent will not see

heyBTW is workspace-scoped. Every query returns only the data inside the workspace whose API key authenticated the request. Cross-company signals appear only when both sides have opted into a collaboration. Full data handling principles are in Data Handling.

​
Write tools

Write tools (push event data, confirm enrichment, update attendee status) are available on Enterprise. See MCP Tools for the full catalog.