Skip to main content

UserEvidence MCP Server

Connect your AI agents to search customer testimonials, case studies, and proof points

T
Written by Tom Aristone


What is MCP?

MCP (Model Context Protocol) is a standardized way for AI assistants to connect to external tools and data sources. Our MCP server lets AI agents search and retrieve your UserEvidence assets—testimonials, case studies, stats, and more—directly within your AI workflows.


Prerequisites

  1. An active UserEvidence account

  2. An MCP-compatible client (Claude web app, Claude Desktop, or custom agent)

Quick Reference

MCP Endpoint

https://app.userevidence.com/mcp?audience=customer

Transport

SSE (Server-Sent Events)

Authentication

OAuth 2.0 (automatic browser flow)

Option 1: Claude Web App (claude.ai)

Recommended for most users. The fastest way to get started—no configuration files needed.
​

Steps

  1. Go to claude.ai and sign in

  2. Click your profile icon in the bottom-left corner

  3. Select Settings

  4. Click Connectors in the left sidebar

  5. Click Add More Integrations

  6. Enter the UserEvidence MCP server URL:
    ​
    ​https://app.userevidence.com/mcp?audience=customer
    ​

  7. Click Add

  8. A browser window will open—sign in with your UserEvidence credential

  9. Once authenticated, UserEvidence tools will appear in your Claude conversations
    ​

Tip: You can verify the integration is active by starting a new chat and asking Claude to search for testimonials. You should see UserEvidence tools being invoked.


Option 2: Claude Desktop App

For users who prefer the desktop application. Requires editing a configuration file.

Steps

  1. Open Claude Desktop

  2. Go to Settings → Connectors → Add custom connector

  3. Fill in the following details:

4. Click “Add”.


​

Option 3: Custom Agents, Frameworks, Other MCP Clients

The UserEvidence MCP server works with any MCP-compatible client or agent framework, not just Claude. If your AI tool supports remote MCP servers, you can connect it using the details below.

What you'll need

Steps

The exact wording varies by client, but the flow is the same everywhere:

  1. Find where your client adds MCP servers or connectors. This is usually under a Settings, Integrations, Connectors, or Tools menu. Frameworks and CLI-based tools typically use a config file instead (often mcpServers in a JSON or YAML file).

  2. Add a new custom/remote MCP server and give it a name (e.g., UserEvidence).

  3. Enter the MCP Server URL above as the endpoint, and select SSE as the transport if your client asks.

  4. Save, then authenticate. A browser window opens for OAuth — sign in with your UserEvidence credentials to authorize the connection.

  5. Confirm the tools loaded. Start a new session and check that the UserEvidence tools appear (many clients have a tools/connectors indicator, or a command like /mcp to list them).

Config-file example:
​
For clients or frameworks that use a configuration file rather than a UI, the entry generally looks like this:
​
json

{
  "mcpServers": {
    "userevidence": {
      "url": 
"https://app.userevidence.com/mcp?audience=customer",
      "transport": "sse"
    }
  }
}


If your tool manages OAuth tokens manually, complete the authorization flow once, store the returned token, and pass it as a Bearer token on later connections — re-authenticating when it expires.


Example Prompts

Once connected, try asking:

  • "Find testimonials from enterprise customers about ROI"

  • "Show me case studies from healthcare companies"

  • "What proof points do we have about implementation speed?"

  • "Find a customer quote for a prospect in financial services"

Troubleshooting

Integration not appearing in Claude

Refresh the page or restart the app. Check Settings → Integrations to verify UserEvidence is listed and enabled.
​

OAuth popup doesn't appear

Check your browser's popup blocker. The OAuth flow requires a popup window to complete authentication.
​

Connection times out

Verify your network allows outbound connections to mcp.userevidence.com on port 443.
​

"Unauthorized" errors

Your OAuth token may have expired. Remove and re-add the integration to re-authenticate.
​

Tools not being invoked

Start a new conversation after adding the integration. Explicitly ask Claude to search UserEvidence to confirm the connection.
​

Need Help?
Contact us at [email protected] with your setup details and any error messages. We're happy to help get you connected.

Related Articles
UserEvidence for Seismic Integration
Proof Recommender
Did this answer your question?