Seismic

Name: Seismic MCP Server
Availability: InStock
Author: Seismic

Productivity3 tools

Search your sales-enablement library and mint trackable LiveSend links from your AI assistant. Three tools in Anthropic's directory, 21 in Seismic's own documentation — and the one write tool produces a URL that works without a login.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Seismic via MCP

https://mcp.seismic.com/claude

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Seismic Tools & Capabilities (3)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The listing shows 3 tools; Seismic documents 21. The published connector is a curated subset by design. If you connect any other way, the surface includes Digital Sales Rooms, meeting transcripts and briefs, and CRM search.
The link the write tool mints does not require a login. externalUrl is an opaque tokenised address. It works for whoever holds it and survives forwarding. recipients is attribution metadata — Seismic's reporting documentation states links created this way have no members.
Nothing is sent, and that is the good news and the limit of it. No delivery step appears in the documented side effects. The agent mints the URL; a human shares it. Minting is still the irreversible half.
Revocation is not publicly documented. Expiry is a documented setting; we found no public endpoint or documented procedure for disabling an already-issued link. Seismic's end-user help site returns Disallow: / in robots.txt, so we did not read it and cannot report what it says.
Link defaults are invisible from MCP. Expiry, password and download settings all fall back to tenant defaults when omitted, and the endpoint that reveals those defaults is not an MCP tool. Set them explicitly rather than trusting a default you cannot inspect.
Recipient-facing disclosure of tracking is not documented publicly. Seismic's materials describe view tracking from the seller's side and are silent on what the viewer is told. Treat that as an open question for your own privacy review.
The directory record carries no permissions field, in front of a tool that publishes internal content externally. Ninth instance of this pattern in this catalogue.
The scope the published connector requests is opaque. seismic.mcp covers search and link generation alike, even though Seismic's own API separates them into seismic.gen-search and seismic.engagement.manage. The consent screen cannot show a boundary the descriptor does not draw.
We could not verify tool behaviour ourselves. The endpoint returned HTTP 401 to an anonymous request on 2026-08-19, so no live inputSchema, readOnlyHint or destructiveHint annotations were readable. Tool names come from Anthropic's snapshot; schemas and descriptions come from Seismic's published documentation.
Permission enforcement in search is a vendor claim. Seismic states results are scoped to the authenticated user's access. We did not authenticate and did not test it.
Prompts are unconfirmed. Anthropic's 2026-08-16 snapshot lists none, and the gated endpoint blocked our own check.
Rate limiting applies underneath. Seismic's specification marks the generate-LiveSend-link operation with a rate limit value of 2. Seismic does not state the unit on that field, so we do not restate it as a per-second figure.

Frequently asked questions

Does the Seismic MCP server send anything when it creates a LiveSend link?

No. Seismic's API documentation lists the side effects of generating a LiveSend link as creating a link record and associating recipients and CRM context — no delivery step appears. The tool returns two URLs and stops; a human still has to share one. The optional recipients field is attribution metadata, not a send list, which Seismic's reporting documentation confirms directly.

Does a Seismic LiveSend link require the recipient to log in?

No, not by default. The tool returns an externalUrl carrying an opaque token, and Seismic's example response shows a bare tokenised address with no sign-in step. Access is bounded by an optional expiry timestamp and an optional password, both settings the caller chooses. Tenant administrators can set default and maximum expiration limits and can make passwords mandatory tenant-wide.

Does Seismic MCP search respect my existing content permissions?

Yes, and Seismic states it plainly. Its MCP documentation says all tool results are scoped to content the authenticated user is authorized to access, and that the server does not expose content outside those permissions. Tenant isolation is enforced at the authentication layer. That is a clearer permissions commitment than most connectors in this catalogue offer, and it is worth crediting.

How many tools does the Seismic MCP server actually have?

Twenty-one are documented; three are listed. Anthropic's directory snapshot names two generative-search tools and LiveSend link generation. Seismic's own documentation tables list twenty-one across LiveSend, Search, Digital Sales Rooms, Meetings and CRM. Seismic explains the gap itself: the published Claude connector exposes a curated subset, while a self-registered custom connector exposes the full set.

What OAuth scopes does the Seismic MCP server request?

One scope, seismic.mcp, at the endpoint Claude actually uses. Seismic's authentication challenge names that per-client descriptor as authoritative, and it advertises exactly that single scope. Seismic warns that this scope alone grants no tool access — a tenant administrator must enable each tool separately for your app, so authorization is split across two independent layers.

Can I use the Seismic MCP connector without an enterprise Seismic account?

No. Seismic has no self-serve signup, and the MCP server adds three further gates. You need a tenant with MCP enabled, which Seismic says requires contacting your customer success manager; the matching Seismic Exchange app installed and enabled in tenant settings; and per-tool permissions granted by a tenant administrator. Individual users cannot enable any of these themselves.

Sources

Seismic MCP Server documentation — https://developer.seismic.com/seismicsoftware/docs/seismic-mcp-server (fetched 2026-08-19 as Markdown via the .md suffix; page last-updated stamp 2026-08-14. Source for the 21-tool count, the published-vs-custom connector comparison, the two-layer permission model, the error reference, the tenant and global endpoints, and the data-and-privacy statement that results are scoped to the authenticated user's permissions) · retrieved 2026-08-19
generate_livesend_link tool schema — https://developer.seismic.com/seismicsoftware/docs/generate_livesend_link (fetched 2026-08-19; full input schema with contents, contexts, recipients and settings, and the output schema returning id, internalUrl and externalUrl) · retrieved 2026-08-19
generative_search_for_retrieving_contents tool schema — https://developer.seismic.com/seismicsoftware/docs/generative_search_for_retrieving_contents (fetched 2026-08-19; default 10 results, maximum 20, isShareable flag, filter grammar) · retrieved 2026-08-19
generative_search_for_answer_or_summary tool schema — https://developer.seismic.com/seismicsoftware/docs/generative_search_for_answer_or_summary (fetched 2026-08-19; returns an answer plus supporting sources) · retrieved 2026-08-19
Generate LiveSend link REST reference — https://developer.seismic.com/seismicsoftware/reference/generatelivesendlink (fetched 2026-08-19; documented side effects list creation only with no delivery step, seismic.engagement.manage scope requirement, rate-limit value 2, and an example response showing a tokenised externalUrl) · retrieved 2026-08-19
Livesend Link Members reporting reference — https://developer.seismic.com/seismicsoftware/reference/reporting-livesendlinkmembersget (fetched 2026-08-19; the sentence establishing that links created through Generate LiveSend Link have no members) · retrieved 2026-08-19
Livesend Viewing Sessions reporting reference — https://developer.seismic.com/seismicsoftware/reference/reporting-livesendviewingsessionsget (fetched 2026-08-19; per-session, per-recipient, per-browser-tab tracking with start and end timestamps) · retrieved 2026-08-19
Get livesend settings reference — https://developer.seismic.com/seismicsoftware/reference/getlivesendsettings (fetched 2026-08-19; tenant default and maximum expiration days, download permission, single-view mode, password complexity policy. Marked legacy by Seismic) · retrieved 2026-08-19
Seismic LiveSend product page — https://www.seismic.com/seismic-live-send/ (fetched 2026-08-19; seller-side engagement tracking including open notifications and per-page view time) · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an initialize request to https://mcp.seismic.com/claude returns HTTP 401 with a zero-length body and www-authenticate: Bearer realm="Seismic" naming the /claude resource descriptor. Sibling probes: /chatgpt 401 with its own descriptor, / 401 with the root descriptor, and /openai, /cursor, /mcp, /anthropic all JSON 404. A descriptor request under a fabricated client name returns 500 with a message naming a missing per-client server configuration file · retrieved 2026-08-19
Live RFC 9728 descriptors — https://mcp.seismic.com/.well-known/oauth-protected-resource/claude and the root form at https://mcp.seismic.com/.well-known/oauth-protected-resource (both fetched 2026-08-19; path-append 200 with scopes_supported: ["seismic.mcp"], root 200 with scopes_supported: ["seismic.engagement.manage", "seismic.gen-search"], both naming https://auth.seismic.com/ as the authorization server. The path-insert form returns 401 with zero bytes) · retrieved 2026-08-19
Live OpenID Connect discovery — https://auth.seismic.com/.well-known/openid-configuration (fetched 2026-08-19; 385 entries in scopes_supported including seismic.mcp, seismic.gen-search and seismic.engagement.manage; PKCE S256; authorization_code, client_credentials and refresh_token among grant types; no registration_endpoint. The RFC 8414 path /.well-known/oauth-authorization-server on that host returns 404) · retrieved 2026-08-19
developer.seismic.com/robots.txt (fetched 2026-08-19) is Allow: / with narrow disallows for edit, login and asset paths, and points to an llms.txt that returns 404. No Content-Signal axes are published, in the file or as a header · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/9feecd5e-241d-4ea1-8caa-289839a3ac04 (snapshot 2026-08-16; three tool names, prompt_names empty, no permissions field present at all, category business-productivity, transport streamable-http) · retrieved 2026-08-16
Seismic's end-user help site, docs.seismic.com, was not usable as a source — its robots.txt is Disallow: /, so LiveSend revocation procedures and recipient-facing tracking disclosure are reported here as undocumented in publicly readable sources