ClutchCall Platform

dev.clutchcallPublished by clutchcall.devOfficial publisherv0.1.0Updated Oct 24, 2026

Tenant-scoped control plane over the ClutchCall platform's full API surface

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant tenant-scoped access to the ClutchCall platform's full API surface as a control plane.

What you can do
  • Exposes the ClutchCall platform's full API surface to the assistant through a single remote MCP endpoint.
  • Acts as a tenant-scoped control plane, so actions are limited to the tenant the access key belongs to.
  • No individual tools are documented in the supplied listing, so the exact operations available are not described here.
When to use it
Worth adding when you already use the ClutchCall platform and want an assistant to work with its API surface directly, scoped to your tenant, instead of calling the API by hand.
Requirements
A remote MCP connection to the ClutchCall portal endpoint over streamable HTTP. OAuth authentication is required: an Authorization header carrying a bearer MCP access key, minted in the console under Settings, API keys, MCP access keys.
Before you install
The server requires a bearer MCP access key in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configurations. Because it fronts the platform's full API surface, the assistant may be able to read or change data within your tenant, so review what the key is allowed to do before connecting.

Installation

In SourceWeft

  1. Open ClutchCall Platform 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/dev.clutchcall%2Fportal/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": {
    "clutchcall-platform": {
      "type": "http",
      "url": "https://portal.clutchcall.dev/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. v0.1.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.