Clamp Analytics

sh.clampPublished by clamp.shOfficial publisherv1.0.0Updated Oct 24, 2026

Clamp Analytics MCP server: traffic, revenue, funnels, cohorts, errors, and search, for AI agents.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote Clamp Analytics MCP server that lets an AI assistant query traffic, revenue, funnels, cohorts, errors and search data.

What you can do
  • Query traffic and revenue metrics from Clamp Analytics
  • Explore funnels and cohorts
  • Inspect errors and search data
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when you want an assistant to pull web analytics figures — traffic, revenue, conversion funnels, cohorts, errors or search performance — into a conversation instead of opening the Clamp dashboard yourself.
Requirements
A remote MCP endpoint at api.clamp.sh over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A Clamp Analytics account with data is implied.
Before you install
Access is granted through OAuth, so the assistant can read whatever analytics data the authorizing account can see; review the scopes granted. No tool list is published, so confirm whether any tools only read data before connecting.

Installation

In SourceWeft

  1. Open Clamp Analytics in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/sh.clamp%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "clamp-analytics": {
      "type": "http",
      "url": "https://api.clamp.sh/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Clamp integrations