Repository navigation
Onboarding request: pilotfish (io.github.gAI-ventures/pilotfish and io.github.gAI-ventures/pilotfish-managed) #3871
Unanswered
NitinReddy-A
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi, please consider onboarding pilotfish to the GitHub MCP Registry (github.com/mcp), following the process described in discussion #1257. Both servers are already published on the Official MCP Registry.
1. pilotfish (open, local)
@gaiventures/pilotfish-mcp, stdio (npx -y @gaiventures/pilotfish-mcp); no account, no API key2. pilotfish managed (remote)
Registry name: io.github.gAI-ventures/pilotfish-managed
Version: 0.1.44 (latest)
Remote endpoint and auth: Streamable HTTP https://pilotfish-be.gai.ventures/mcp, OAuth sign-in or API key; stdio relay
@gaiventures/pilotfish-mcp-managedRepository: https://github.com/gAI-ventures/pilotfish-mcp (subfolder packages/mcp-managed)
License: MIT
What it does: Runs whole web tasks on a cloud browser from any MCP agent and returns the result (optionally JSON matching a schema), with saved logins, scheduled tasks, replays and a hand-off to the person for sign-ins and codes.
Verification: https://registry.modelcontextprotocol.io/v0.1/servers?search=gAI-ventures shows both servers active on the Official MCP Registry, while https://api.mcp.github.com/v0.1/servers?search=pilotfish returns no results yet.
Thanks for considering it.
All reactions