shre.me

me.shrePublished by shre.meOfficial publisherv1.0.0Updated Oct 28, 2026

Turn long URLs into shre.me/code, and read the clicks: day, country, device, referrer.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote shre.me server that lets an assistant shorten long URLs into shre.me links and read click statistics such as day, country, device and referrer.

What you can do
  • Shorten long URLs into short shre.me links with a generated code.
  • Read click statistics for a link, broken down by day, country, device and referrer.
  • No tool list is published, so the exact set of operations is not documented; the description covers link creation and click reporting only.
When to use it
Useful when you want an assistant to create shareable short links and then report on how they perform, for example summarizing traffic by country or device for a campaign or post.
Requirements
A remote endpoint at over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so a shre.me account and a client that supports the OAuth flow are needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so it receives access to your shre.me account. Creating short links publishes them publicly, and click statistics reveal visitor data such as country, device and referrer to the assistant. No tool list is published, so confirm what the server can change before connecting.

Installation

In SourceWeft

  1. Open shre.me 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/me.shre%2Fshre/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": {
    "shre-me": {
      "type": "http",
      "url": "https://www.shre.me/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

56% 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

    Publish an icon in the registry entry.

  • 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.