Skip to main content

Connect Testimonial with AI agents

Sign in to connect Claude, Grok, ChatGPT, or Cursor. Paste https://mcp.testimonial.to only. Access token / API key is a fallback under Advanced. Notion uses a header token.

Written by Damon Chen

Connect Testimonial to Claude, Grok, ChatGPT, or Cursor by signing in in the browser. Paste the server URL only — do not append an access token. Notion uses a header token.

Sign-in is the default. Use an access token or API key only as a fallback under Advanced (API key / access token) in AI & Agents.

The page reads: “Give AI assistants access to your testimonials, case studies, and NPS data so they can browse, search, and manage them for you.” MCP (Model Context Protocol) is the connection method. There is no sidebar item named MCP.

Find AI & Agents

The control lives on a Space, not on Settings. The Space sidebar order is Overview, Inbox, Import, Brand monitor, Case studies, NPS, Automation, AI & Agents, Embed widgets, Pages, then SPACE SETTINGS.

  1. Open a Space from the Dashboard.

  2. In the left sidebar, click AI & Agents.

  3. Choose a card: Claude, Grok, ChatGPT, Cursor, or Notion.

Card lines on the page:

  • Claude — Browse and manage testimonials from Claude

  • Grok — Browse and manage testimonials from Grok

  • ChatGPT — Browse and manage testimonials from ChatGPT

  • Cursor — Query your testimonial data from your IDE

  • Notion — Use Notion agents to browse and manage your testimonials

Claude, Grok, ChatGPT, and Cursor connect by signing in. Notion uses a header token. Access token / API key is a fallback under Advanced (API key / access token).

Note: If AI & Agents is locked or missing, check Settings → Plan, or message us in the chat widget.

Connect by signing in

Add the hosted MCP server, paste the URL only, then sign in and approve in the browser. You do not generate an access token for this path.

The hosted server is:

https://mcp.testimonial.to

  1. In Claude, Grok, ChatGPT, or Cursor, add a connector.

  2. Paste https://mcp.testimonial.to. Do not append an access token.

  3. Add the connector.

  4. The client opens a browser.

  5. Sign in to testimonial.to if you are asked.

  6. Review the page titled Connect to testimonial.to. It lists what the client wants access to. Authorize stays disabled until the page is ready.

  7. Click Authorize to allow the connection, or Cancel to deny it.

The consent page covers reading your testimonials, mentions, and analytics; managing your Wall of Love and the automation routes you configure; and acting only within the access you approve.

Cancel denies the client connection. The client does not get access.

If the request is invalid or missing required details, the page shows an error with a Back to Settings link.

Note: Do not add an access token to the URL or headers when you use this path.

If you already connected with an older server URL, that connection still works. New setups should use https://mcp.testimonial.to.

Claude

  1. On AI & Agents, open the Claude card.

  2. In Claude, go to Connectors and add a custom connector, or use the in-product link.

  3. Paste https://mcp.testimonial.to. Do not append an access token.

  4. Add the connector, then sign in and approve on Connect to testimonial.to.

Or use the Claude Code command:

claude mcp add testimonial --transport http --url "https://mcp.testimonial.to"

Note: If Claude Code CLI cannot sign in in the browser, generate an access token under Advanced (API key / access token).

Grok

  1. On AI & Agents, open the Grok card.

  2. In Grok, open Plugins.

  3. Open Connectors.

  4. Add a connector and paste https://mcp.testimonial.to. Do not append an access token.

  5. Add the connector, then sign in and approve on Connect to testimonial.to.

Note: Custom connectors need a paid Grok plan. If Grok sign-in fails, use the tokenized server URL under Advanced (API key / access token).

ChatGPT

  1. On AI & Agents, open the ChatGPT card.

  2. In ChatGPT, turn on Developer Mode under Settings → Security and login.

  3. Add a connector and paste https://mcp.testimonial.to. Do not append an access token.

  4. Add the connector, then sign in and approve on Connect to testimonial.to.

Note: If ChatGPT sign-in fails, use the ChatGPT tokenized server URL under Advanced (API key / access token).

Cursor

  1. On AI & Agents, open the Cursor card.

  2. In Cursor, go to Settings → Tools & MCP → Connect.

  3. Paste https://mcp.testimonial.to. Do not add an Authorization header or access token.

  4. Connect, then sign in and approve on Connect to testimonial.to.

Cursor config for this path:

{  "mcpServers": {    "testimonial": {      "url": "https://mcp.testimonial.to"    }  }}

Note: Access renews automatically for about 30 days of use. Reconnect if access is revoked or the connector sits idle longer than that.

Connect Notion

Notion uses a header token. It does not use the sign-in path above.

  1. On AI & Agents, open the Notion card and generate a token.

  2. In Notion, go to Settings → Connections → MCP Tools → Add tool.

  3. Authenticate with a custom header. Use the server URL and the Bearer token from the card.

  4. Verify by asking a Notion Agent to list your Testimonial spaces.

Note: Do not paste the token into a public chat, a ticket, or a shared screenshot.

Advanced (API key / access token)

This is a fallback, not the default path. Claude, Grok, ChatGPT, and Cursor should sign in with the URL only. Use an access token or API key for Claude Code CLI, a client without browser sign-in, or the Notion-style header path.

  1. Open AI & Agents and expand Advanced (API key / access token) on the client card.

  2. Choose an expiry: 15 minutes, 1 hour, 6 hours, 12 hours, 1 day (default), 7 days, 30 days, or Never expire.

  3. Click Generate token. Generate a new token when you need to replace one.

There is no dedicated Copy-token button. After the token is generated, paste it into the client config in place of <ACCESS_TOKEN>. Send it as a Bearer header or as ?accessToken= on the server URL. Keep the token private. The page warns: “This URL includes your access token, so keep it private.”

Cursor Bearer config for this path:

{  "mcpServers": {    "testimonial": {      "url": "https://mcp.testimonial.to",      "headers": {        "Authorization": "Bearer <ACCESS_TOKEN>"      }    }  }}

ChatGPT

If ChatGPT sign-in fails, generate a token under Advanced (API key / access token), then copy the ChatGPT tokenized server URL.

Note: Fallback if ChatGPT OAuth fails: paste this tokenized URL as the Remote MCP server URL and skip OAuth / leave authentication off.

Grok has the same fallback: after you generate a token under Advanced (API key / access token), copy the tokenized server URL and paste it as the Remote MCP server URL.

Existing token connections may still need a new access token before analytics, usage, automation-route, or Brand Monitor keyword tools work. Those tools can appear in an older connection and still return errors until you regenerate the token in AI & Agents and reconnect. Existing tokens keep their previous permissions until you do that. New connections get the keyword tools automatically.

Note: Do not paste the token into a public chat, a ticket, or a shared screenshot.

What an agent can do

Each client card lists the same capabilities. After you connect, the agent can:

  • Browse and search your testimonials

  • Add or remove items on your Wall of Love

  • List Brand Monitor mentions for a Space, filtered by platform, sentiment, and discovery date

  • Open one mention by ID

  • Ignore a mention so it leaves the discovered list

  • List, add, and delete Brand Monitor keywords for a Space

  • Analyze testimonial, mention, and NPS trends over time

  • Compare spaces and check plan usage and quota

  • Generate case studies from testimonials

  • Check NPS scores and survey responses

  • Browse saved case studies and answers

  • Set up standing automation routes that keep running after the chat ends

  • List, open, create, update, and delete routes for a Space

  • Test a filter against recent mentions before turning a route on

  • Search the Space owner’s connected Slack workspace to pick a channel

Each card also has a collapsed See example prompts section.

Standing automation routes

A route watches a source, applies optional filters, then runs an action. It keeps running after the chat ends.

Sources:

  • A new Brand Monitor mention

  • A new testimonial

  • An NPS response

Actions:

  • Post to a Slack channel

  • Add the item to your Wall of Love. This only happens if the Space does not require confirmation. The default is not to publish without confirmation.

  • Send a case study request invite

  • Send the event to a webhook

You can filter by sentiment, platform, intent tags, and minimum rating. For intent tags, the route matches a mention that has any of the tags you select. For example, you can send Reddit mentions with a buy-intent tag to a Slack channel. New Brand Monitor mentions can include intent tags. Older mentions stay without tags until a new scan picks them up again.

For NPS, leaving the rating filter empty matches detractor scores 0–6. Set a minimum rating when you want promoters.

A route runs when the source event happens. Brand Monitor mention routes follow Brand Monitor scans, which already run about daily.

Slack and webhook destinations need Ultimate. Case study request invites are unlimited on Ultimate+. Plans below Ultimate+ get a one-time free case study invitation for the account.

To post to Slack or pick a channel, connect Slack under Automation → Slack. If Slack is already connected, reconnect there. Until you do, the agent cannot post or list channels.

To review mentions in the product, see Brand Monitor. To connect Slack, see Integrating Slack with Testimonial.

Note: Use the tool list your connected agent shows. Names can change as we add coverage. If analytics, usage, automation-route, or Brand Monitor keyword tools still error on an existing token connection, generate a new token and reconnect. New connections get the keyword tools automatically.

Plans

Current plan names are Free, Starter, Ultimate, and Ultimate+. Ultimate and Ultimate+ are billed per Space.

On an Ultimate Space, AI & Agents showed no plan-gate or upgrade copy. This article does not invent a plan requirement. If the page is locked, check Settings → Plan.

Slack and webhook destinations on a route need Ultimate. Case study request invites are unlimited on Ultimate+. Plans below Ultimate+ get a one-time free case study invitation for the account.

The REST API, webhooks, and Zapier are a separate integration path from this MCP server. A Space API key can also list, open, and ignore Brand Monitor mentions. See the related articles below.

Related

Need help? Message us in the chat widget.

Did this answer your question?