Koskamo

Tessamonials MCP

The Tessamonials MCP server enables AI assistants to manage customer voice interviews and testimonials. It allows agents to set up collection campaigns, prepare and send invitations, read interview responses and transcripts, and manage testimonial approvals and visibility. The connector uses OAuth 2.0 with PKCE for secure authentication, ensuring the assistant acts within the user's existing permissions and role-based access controls.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Tessamonials MCP logo, by TessamonialsVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-10-26Operated by Tessamonials
You need:Sign-in OAuth 2.0 with PKCE and dynamic client registrationSign in with the email code or Google sign-in you already use for TessaMaking it public requires the Pro plan
MCP endpoint (Streamable HTTP)
https://tessamonials.com/mcp
Vendor documentation

What you can do with it

  • Set up and manage customer interview campaigns
  • Read interview responses and transcripts
  • Approve and manage customer testimonials
  • Prepare and send invitation links

Source and maintenance

Vendor evidenceRegistry 0.1.0

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http tessamonials-mcp https://tessamonials.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add tessamonials-mcp --url https://tessamonials.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tessamonials-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "tessamonials-mcp": {
      "url": "https://tessamonials.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "tessamonials-mcp": {
      "type": "streamableHttp",
      "url": "https://tessamonials.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tessamonials-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "tessamonials-mcp": {
      "type": "http",
      "url": "https://tessamonials.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http tessamonials-mcp https://tessamonials.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "tessamonials-mcp": {
      "url": "https://tessamonials.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "tessamonials-mcp": {
      "serverUrl": "https://tessamonials.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Tessamonials MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Tessamonials MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing