Banana Peel

io.github.ygdotcomPublished by GitHub account ygdotcomv0.1.1Updated Oct 24, 2026

OpenRouter for browser agents. One MCP to route browser tasks across 250+ runners.

VerifiedSTDIODesktop onlyBrowser AutomationAI & ML

Overview

AI-generated overview

Routes browser-agent tasks across a large pool of runners, acting as an OpenRouter-style router for browser automation.

What you can do
Banana Peel is a local MCP server that routes browser tasks to one of 250+ runners, described as an OpenRouter-style router for browser agents. The manifest does not list individual tools, so the exact tool surface is not documented here. It runs as a local process over stdio and authenticates with a single API key.
When to use it
Worth considering when an assistant needs to perform browser tasks and you want a routing layer that can dispatch them across many runners instead of a single browser backend. It is desktop-only, so it is not suitable for web-hosted or headless server use.
Requirements
A local runtime able to launch the packaged MCP server over stdio, on a desktop machine. A Banana Peel API key supplied through the BANANA_PEEL_API_KEY environment variable; the manifest notes agents can mint one with the Banana Peel CLI. Network access to the routing service.
Before you install
The server requires a secret API key (BANANA_PEEL_API_KEY) and routes browser tasks to third-party runners, so task content and target pages may be shared with those runners. Browser automation can act on live sites, including logging in, submitting forms, or changing data. Review what the key authorizes before installing.

Installation

In SourceWeft

  1. Open Banana Peel in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.