Back to Browse

Platform MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://mcp.sherweb.com

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-sherweb-platform": {
      "url": "https://mcp.sherweb.com"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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).

Reviews

No reviews yet

Be the first to review this server!