pilotfish (managed)

io.github.gAI-venturesPublished by GitHub account gAI-venturesv0.1.4Updated Nov 5, 2026

Your pilotfish account for any MCP agent: tasks in pilotfish's cloud browser, saved logins, replays.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBrowser Automation

Overview

AI-generated overview

Connects an MCP agent to a pilotfish account so it can run tasks in pilotfish's cloud browser, use saved logins and review replays.

What you can do
  • Run tasks in pilotfish's cloud browser on behalf of the connected account.
  • Use saved logins stored in the pilotfish account.
  • Review replays of previous browser sessions.
  • Reach the same account either through the hosted endpoint or a local npm package over stdio.
When to use it
Useful when an assistant should carry out browser work in a managed cloud browser tied to an existing pilotfish account, including sites where saved logins are needed, and when session replays matter for checking what happened.
Requirements
A pilotfish account and either OAuth sign-in or an MCP key (pf_...) from the app's Connect an agent page, supplied as PILOTFISH_KEY or as an Authorization bearer header. The hosted endpoint is by default and can be changed with PILOTFISH_URL; the local option is the npm package @gaiventures/pilotfish-mcp-managed, which needs Node.js. Network access is required.
Before you install
The server acts on a real pilotfish account: tasks run in a cloud browser with the account's saved logins, so the assistant may act on sites while signed in. Treat the MCP key as a secret and keep it out of shared configuration; OAuth can be used instead of embedding the key. Browser sessions are recorded as replays, so activity may be stored and reviewable.

Installation

In SourceWeft

  1. Open pilotfish (managed) 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.github.gAI-ventures%2Fpilotfish-managed/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": {
    "pilotfish-managed": {
      "type": "http",
      "url": "https://pilotfish-be.gai.ventures/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

2
  1. v0.1.4LatestNov 5, 2026
  2. v0.1.1Nov 5, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.