6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search your sales-enablement library and mint trackable LiveSend links.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Seismic MCP server connects Seismic's sales-enablement library to Claude, ChatGPT and any MCP-compatible agent. Two tools search your battlecards, decks and pricing sheets; the third mints a LiveSend link — a trackable URL that opens without a login. Sign-in is OAuth, and a Seismic administrator must enable every tool first.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.Disallow: / in robots.txt, so we did not read it and cannot report what it says.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.inputSchema, readOnlyHint or destructiveHint annotations were readable. Tool names come from Anthropic's snapshot; schemas and descriptions come from Seismic's published documentation.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.
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.
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.
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.
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.
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.
.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-19generate_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-19generative_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-19generative_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-19seismic.engagement.manage scope requirement, rate-limit value 2, and an example response showing a tokenised externalUrl) · retrieved 2026-08-19initialize 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-19scopes_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-19scopes_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-19developer.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-19prompt_names empty, no permissions field present at all, category business-productivity, transport streamable-http) · retrieved 2026-08-16docs.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 sourcesConnect Seismic once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.