Book a demo
Menu

Glossary

Model Context Protocol (MCP)

The Model Context Protocol (MCP) is an open standard that lets an AI assistant connect to outside tools and data through servers that describe what the assistant can read and do.

Anthropic introduced MCP in 2024, and assistants including Claude and ChatGPT now support it. Add a product that runs an MCP server to any of them as a connector. Then ask about your own data in the assistant you already use.

What is an MCP server?

An MCP server is the product side of the connection. It publishes a list of tools, each with a name, a description, and the inputs it takes, and your assistant decides when to call them. Reading tools answer questions. Acting tools change something, such as drafting an email or updating a record.

What does MCP do for your event team?

Your event data usually sits in several places: the event plan, the attendee list, captured conversations, and the CRM. With MCP, ask your assistant questions that cross them. Which target accounts at a show still need an owner? Which leads from last week still need a follow-up?

What should you let an MCP connection do?

Reading and acting carry different risks. When an assistant can read private data and act somewhere else, the text it reads can steer it. So make acting tools wait for a person, and let each connection see only what the signed-in person can see. An approval gate is one way to set that.

How do you use FieldXM MCP?

Add FieldXM MCP to Claude or ChatGPT, and your assistant gets tools for your events, account plans, leads, conversation notes, and follow-ups. It answers your questions at once, and its actions follow the same approval rules as Ask FieldXM. See the connector and its tools on the FieldXM MCP page.

Related terms

  • Approval gateAn approval gate is a rule in FieldXM that sets how much autonomy an action that changes records gets, from always ask first to act autonomously; the team chooses the level, and FieldXM logs it.
  • Ask FieldXMAsk FieldXM is the assistant in FieldXM's web app, a side panel on every page that answers from the team's own events, accounts, contacts, and conversations, scoped to the page the user is on.
  • CRM write-backCRM write-back is the outbound half of a CRM integration, the step where a connected tool creates or updates CRM records such as contacts, companies, notes, and event attendance.
  • Account workspaceThe account workspace is FieldXM's view of the accounts behind an event's attendees, which it labels by where each stands in the CRM, tiers by ICP fit, gives an owner, and checks for coverage gaps.
  • Captured contactsCaptured contacts are the leads your reps capture in the FieldXM mobile app, shown in the event's account workspace in the web app beside the accounts they belong to.

See it in FieldXM

  • FieldXM MCPConnect Claude, ChatGPT, or any MCP-ready assistant to your events, accounts, and leads. You set the approval rules for anything it changes.

Browse