> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/seismic.md).

# Seismic

Connect your company's Seismic instance to Cakewalk so agents can search content, retrieve meeting intelligence and access CRM context through the gateway.

Connect your company's Seismic instance to Cakewalk's MCP Gateway. Every agent tool call against Seismic passes through the gateway and is evaluated against your Policies.

## Requirements

* Seismic admin who can register apps at <https://apps.seismic.com> and enable apps in Seismic Web.

## Required Scopes

OAuth scope the app must request:

```
seismic.mcp
```

This scope is selected by default during app creation.

## Step 1: Create the OAuth App

1. Sign in at <https://apps.seismic.com>.
2. Click **+ Create an App**.
3. Enter an app name, select **MCP app** as the type, then click **Create app**.

## Step 2: Enable OAuth

1. Toggle the authentication switch on (off by default).
2. Select **OAuth2 - Authorization Code Flow**.

## Step 3: Configure the Redirect URI

In the **Redirect URIs** field, enter:

```
https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback
```

## Step 4: Generate the Client Secret

1. Click **Generate** to create the client secret.
2. Copy the secret immediately. Seismic shows it once.

Confirm **seismic.mcp** is selected in the scope picker (it is by default), then save the app.

## Step 5: Enable the App in Seismic

1. Open **Seismic Web**.
2. Go to **Admin Settings** > **My Apps**.
3. Find your app and click **Enable App in Seismic**.
4. Accept the consent modal.

## Step 6: Paste Credentials Into Cakewalk

1. Open <https://app.getcakewalk.io>.
2. Go to All Connections.
3. Find Seismic.
4. Click Edit credentials.
5. Paste the Client ID and Client Secret from your Seismic app's Auth configuration page.
6. Save.

## Verifying It Works

The Seismic Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to search Seismic content. If Seismic returns results, the Connection is live.

## Troubleshooting

* Invalid redirect URI on consent: confirm the **Redirect URIs** entry matches `https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback` exactly.
* Tools return permission errors: the **seismic.mcp** scope must be selected, and the app must be enabled in Seismic Web (Step 5).

## Learn More

* [Create an app with authentication](https://developer.seismic.com/seismicsoftware/docs/create-an-app-with-auth)
* [Seismic MCP server](https://developer.seismic.com/seismicsoftware/docs/seismic-mcp-server)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/seismic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
