The Seismic MCP Server exposes Seismic sales enablement capabilities as tools that AI agents and assistants can invoke natively. It implements the Model Context Protocol (MCP) specification version 2025-06-18 over Streamable HTTP transport — an open standard for connecting AI models to external data and actions — allowing agents to search content, generate LiveSend links, retrieve meeting intelligence, and look up CRM context directly within an AI conversation, without custom API integrations.

📘

Early Access

The Seismic MCP Server is currently in Early Access. To get access, reach out to your Customer Success Manager.

Before You Begin

Ensure you have the following before connecting:

• A Seismic tenant with MCP enabled (contact your CSM if not yet enabled)
• An MCP-type app created in the Seismic App Registry Portal — this provides the OAuth client credentials needed to obtain a user access token
• A user access token with the seismic.mcp scope (see Authentication)
• Tool access enabled for your app by a tenant administrator (see Tool Permissions)
• An MCP-compatible client (see Supported Clients)

Supported Clients

The Seismic MCP Server has been validated with the following AI clients:

Any client that supports the MCP 2025-06-18 specification over Streamable HTTP transport will work with this server.

Endpoints

Tenant endpoint

https://mcp.seismic.com/v1/tenants/<tenant_name>

• Automatically resolves the tenant from the URL path
• Recommended for most integrations

Global endpoint

https://mcp.seismic.com/v1

• Uses central authentication
• The user is prompted to provide their tenant name during the OAuth flow

Quick Start

Add the following to your MCP client configuration, replacing <tenant_name> and <access_token>:

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "seismic": {
      "type": "http",
      "url": "https://mcp.seismic.com/v1/tenants/<tenant_name>",
      "headers": {
        "Authorization": "Bearer <access_token>"
      }
    }
  }
}

Generic MCP HTTP client

POST https://mcp.seismic.com/v1/tenants/<tenant_name>
Content-Type: application/json
Authorization: Bearer <access_token>

The server responds using the standard MCP Streamable HTTP protocol. See MCP client documentation for client-specific setup details.

Authentication

All requests require a Seismic JWT user access token.

Authorization: Bearer <access_token>

Scope requirements:

⚠️

The seismic.mcp scope alone does not grant permission to invoke tools. Tool invocation requires additional permissions configured by your tenant administrator. See Tool Permissions.

Obtaining OAuth Credentials

1. Create an MCP-type app in the Seismic App Registry Portal
2. Use the provided client_id and client_secret to request a user access token via the standard OAuth 2.0 authorization code flow
3. Include seismic.mcp in the requested scopes

See Creating and Installing an MCP app in Seismic for step-by-step instructions.

Tool Permissions

The Seismic MCP Server uses a two-layer permission model:

Layer 1 — Tenant-level enablement
A tenant administrator must explicitly enable each tool for your MCP app in the Seismic App Registry Portal. Tools that are not enabled will return a TOOL_NOT_ALLOWED error when invoked.

Layer 2 — Feature availability
Some tools depend on Seismic features being active on your tenant (for example, Generative Search requires the Generative Search feature to be provisioned). If a required feature is not enabled, the tool will be unavailable regardless of permissions.

📘

Administrator actions

Tenant administrators can manage tool access per MCP client app via the Seismic App Registry Portal under MCP App Permissions.

Available Tools

Search

Livesend

Meetings

DSR

CRM

📘

Tool Schema

Check the individual tool documentation for input and output schema information.

Error Reference

All errors follow a structured format with a code field identifying the specific failure.

{
  "error": {
    "code": "TOOL_NOT_ALLOWED",
    "message": "The requested tool is not available for this tenant. Please contact your administrator to enable it.",
    "correlationId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  }
}

❗️

Reporting errors to support

When contacting support about an error, always provide the full response payload including the correlationId. This is the primary identifier used to trace the request in server logs and is essential for diagnosis.

Usage Examples

Content discovery and answers

Suggest some best practices for enterprise sellers, include sources

How is the SEP market evolving? Answer from my Seismic contents

Find the latest competitive battlecard for Salesforce

Content sharing with LiveSend

Generate a LiveSend link for the Q1 product overview deck

Create a shareable link for the Mars Case Study with tracking enabled

Meeting intelligence

Summarise my last meeting with Acme Corp

What objections came up in the Acme deal review last Tuesday?

Show me action items from yesterday's QBR

What topics were discussed in the meeting with ID abc-123?

CRM-connected workflows

What DSRs are associated with the Acme opportunity?

Show me the content shared in recent meetings for the Salesforce account

Find CRM context for opportunity ID 00646000009eMGL

Data & Privacy

• All tool results are scoped to content the authenticated user is authorized to access within Seismic. The server does not expose content outside the user's permissions.
• The MCP Server acts as a proxy to Seismic's existing APIs. No user data is stored by the MCP Server beyond what is logged for audit and observability purposes.
• Tenant isolation is enforced at the authentication layer — users can only access data within their own Seismic tenant.
• For full data processing and privacy details, see the Seismic Trust Center.

Support

For integration help, contact your Customer Success Manager or reach out via https://www.seismic.com/contact/.