Webshare

io.websharePublished by webshare.ioOfficial publisherv1.0.1Updated Oct 24, 2026

Manage your Webshare proxies, usage, plans and billing. Sign in with OAuth, no API key.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Remote Webshare MCP server that lets an assistant manage proxy services, usage, plans and billing through an OAuth sign-in.

What you can do
  • Manage proxies: view and administer the proxy services on a Webshare account.
  • Check usage: review consumption and related account activity.
  • Review plans and billing: look at subscription plans and billing information.
  • Sign in with OAuth rather than supplying an API key.
When to use it
Useful when you already have a Webshare account and want an assistant to check proxy usage, review plans or billing, or manage proxy settings without handling an API key manually.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. A Webshare account with OAuth sign-in is required, and network access to the hosted endpoint.
Before you install
The server is authorized through OAuth and can reach account-level proxy, usage, plan and billing data, so grant access only to a trusted client. Actions that change proxies, plans or billing may affect paid services; confirm before letting an assistant make changes.

Installation

In SourceWeft

  1. Open Webshare 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/io.webshare%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": {
    "webshare": {
      "type": "http",
      "url": "https://mcp.webshare.io/"
    }
  }
}

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

2
  1. v1.0.1LatestOct 2, 2026
  2. v1.0.0Sep 29, 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.