Rigshare
Let your coding agent search RIGShare listings and manage bookings for GPUs, robots, drones, and heavy gear when you rent capacity instead of buying hardware.
Overview
io.github.RPER2001/rigshare is a MCP server for the Operate phase that connects agents to RIGShare to browse and book rented GPUs, robots, drones, and construction equipment.
What is this MCP server?
- Marketplace MCP for renting GPUs, robots, drones, and construction equipment on RIGShare
- Four public read-only tools work without RIGSHARE_API_KEY
- Authenticated tools: list my bookings, list my sessions, create booking (Bearer API key)
- Owner onboarding flows described for listing gear—not only renter flows
- npm package rigshare-mcp v1.1.2 over stdio
- 4 public read-only MCP tools without API key
- 3 authenticated tools requiring RIGSHARE_API_KEY
- Package version 1.1.2 (rigshare-mcp)
What problem does it solve?
You need short-term GPUs or physical gear but manually browsing a rental marketplace breaks the flow of agent-assisted shipping and ops.
Who is it for?
Indie ML or robotics builders who rent RIGShare capacity episodically and want booking steps inside Claude Code or Cursor.
Skip if: Builders locked into a single cloud provider with fixed contracts and no interest in third-party equipment rental APIs.
What do I get? / Deliverables
Your agent can query RIGShare via MCP, use public tools without a key, and create or review bookings once RIGSHARE_API_KEY is configured.
- Agent-driven RIGShare listing search via public MCP tools
- Booking and session visibility when API key is set
- Path to onboard owned equipment on RIGShare (platform feature referenced by server)
Recommended MCP Servers
Journey fit
Equipment rental and session booking sit in Operate/infra: you are sourcing runtime capacity for experiments, training, or field work after you know what to build. Infra is the right shelf because RIGShare is an external compute and physical-equipment marketplace accessed via API/MCP, not app frontend code.
How it compares
Rental-marketplace MCP API—not a GPU cluster provisioner skill or generic cloud IaC pack.
Common Questions / FAQ
Who is io.github.RPER2001/rigshare for?
It is for developers and owners using RIGShare who want MCP agents to search equipment and, with an API key, manage bookings and sessions.
When should I use io.github.RPER2001/rigshare?
Use it in Operate when you are arranging rented GPUs, robots, drones, or construction gear and want the agent to call RIGShare instead of switching to the web app.
How do I add io.github.RPER2001/rigshare to my agent?
Install rigshare-mcp from npm as a stdio server, add it to your MCP client config, and set RIGSHARE_API_KEY only if you need rigshare_list_my_bookings, rigshare_list_my_sessions, or rigshare_create_booking; keys are available at https://www.rigshare.app/profile#api-keys.