Sherweb Platform MCP Server

com.sherwebPublished by sherweb.comOfficial publisherv1.52.10Updated Nov 2, 2026

Sherweb Platform MCP server to manage subscriptions and orders. Use OpenID Connect to authenticate.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote Sherweb Platform MCP server that lets an assistant manage subscriptions and orders through Sherweb's internal APIs.

What you can do
  • Manage subscriptions and orders on the Sherweb platform through Cumulus MCP tools exposed by the server.
  • Discover tools by prompting in natural language, and use prompt templates through slash commands.
  • Read-only operations run after a single consent per session; write operations ask for consent on every execution.
When to use it
Useful for Sherweb partners or customers who want an AI assistant to look up and act on their platform subscriptions and orders without leaving the chat client.
Requirements
A remote streamable HTTP endpoint at the provider's MCP server address; no local package or runtime. Authentication is required via OpenID Connect, using either authorization code with PKCE or client credentials flow, so an appropriate Sherweb account or client registration is needed.
Before you install
The server performs backend requests on behalf of the authenticated user or client, and non-read-only operations are audited. Write operations change subscriptions or orders and require consent on every execution, so review each confirmation before approving.

Installation

In SourceWeft

  1. Open Sherweb Platform MCP Server 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/com.sherweb%2Fplatform/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": {
    "sherweb-platform": {
      "type": "http",
      "url": "https://mcp.sherweb.com/"
    }
  }
}

README

Platform MCP Server

Overview

This is the MCP server exposing Cumulus MCP tools, prompts (templates) and resources, leveraging Sherweb internal APIs.

Usage

Connect to the MCP server URI at https://mcp.sherweb.com for streamable HTTP transport. Tools can then be discovered by the agent when prompting in natural language. Prompt templates can also be used with slash commands. Follow the steps in this knowledge base article for a successful journey.

Authentication

The authentication uses OpenID Connect with either the authorization code with PKCE flow or the client credentials flow. See the protected resource document for details.

[!CAUTION] It is important to understand the MCP server performs requests in the backend on behalf of authenticated entity (user or client depending on the flow) and when operations are audited (usually non-readonly tool methods)

Consent

Consent is a key principle of the MCP specification, so human oversight (aka human-in-the-loop or HITL) is maintained. Usually, managing consent is an MCP client responsibility, but it is implemented in this server also, with the following variants:

  1. for read operations, the consent is asked once per session and scoped for all read-only tools
  2. for update (write) operations, the consent is asked for every tool for every execution (this may seem to hinder the UX, but increases user control over the AI agent).

Source: README.md at commit 50f8373

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.52.10LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Sherweb integrations