Pebble

com.shippebblePublished by shippebble.comOfficial publisherv1.0.0Updated Oct 24, 2026

Host the tools your AI builds — small internal tools in isolated microVMs, live for your team.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Pebble is a remote MCP endpoint that lets an assistant host small internal tools in isolated microVMs for a team.

What you can do
Pebble is a hosted MCP server reachable at a remote endpoint. According to its registry description, it hosts tools built with AI as small internal tools running in isolated microVMs and makes them live for a team. No individual tools are listed in the supplied manifest, so the exact operations an assistant can call are not documented here.
When to use it
Consider it when you want an assistant to deploy or manage small internal tools for a team rather than run them locally. It is a hosted service, so it suits users who prefer a remote endpoint over a local package.
Requirements
A remote MCP endpoint at the provider's site, reached over streamable HTTP. Authentication is OAuth and is required. No environment variables, headers, or packages are declared.
Before you install
The server is a third-party hosted service, so tool code and any data passed to it leave your machine. OAuth grants the server access under your account, and the manifest does not describe what it stores or shares. No tool list is provided, so review the provider's terms and permissions before connecting.

Installation

In SourceWeft

  1. Open Pebble 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.shippebble%2Fpebble/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": {
    "pebble": {
      "type": "http",
      "url": "https://shippebble.com/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.