MCP Servers - A high-level walkthrough

Think of it like a power outlet for AI

Your AI assistant (Claude, Copilot, Cursor, etc.) is smart — but out of the box, it only knows what's in its context window. It can't reach into Seismic, pull a relevant piece of content, or generate a LiveSend link unless you give it a way in.

Seismic's MCP Server is that way in. It's a standardized bridge that lets any MCP-compatible AI client connect to Seismic and do things — not just talk about things.

What it actually does

Once connected, an AI agent can call Seismic tools like real actions:

Search for content using natural language ("find me a competitive battlecard for Salesforce")
Generate answers from Seismic's knowledge base, with sources cited
Create a LiveSend link on the spot, configured and ready to share

The AI doesn't need a custom Seismic integration. It just needs to know the MCP Server exists, and it can discover and invoke the right tools automatically.

Why it matters

Most AI integrations are one-offs — someone hard-codes a connection between two systems and it breaks when either side changes. MCP is a standard protocol, like HTTP for AI tools. Build once, connect to any compatible client.

For sales teams, this means the AI assistant already living in your workflow can now pull from Seismic without you switching tabs, running a search, or copy-pasting anything. Ask your AI to prep for a meeting, and it can surface the right content from Seismic as part of that answer.

What you need to get started

The barrier is low, but there are a few gates:

An MCP-compatible client — tools like Claude Desktop, Cursor, or any agent framework that supports MCP
A Seismic account with the right scope enabled — your tenant admin controls which tools are available
An MCP app registration — created in the Seismic App Registry, this gives your client the credentials to authenticate
Tool approvals — each tool (search, LiveSend, etc.) requires its own permission to be granted; without them, the server connects but exposes nothing

Think of the tool permissions like room keys in a hotel. The MCP connection gets you into the building. The permissions decide which rooms you can open.