Search, inspect, and book RIGShare equipment rentals, list your bookings and remote sessions, and get owner onboarding via MCP.
Search active listings across construction and Robotics & AI with filters (division, category, price, location, remote access, sort, pagination).
Get full details for one equipment listing, list categories with counts, and fetch owner onboarding pitch/signup.
List your bookings and remote sessions (requires API key with bookings:read / sessions:read).
Create a booking for equipment with server-computed pricing, duration/pickup options, and idempotency (requires bookings:write).
Model Context Protocol server for RIGShare. Browse construction equipment and Robotics & AI hardware rentals from any MCP-compatible AI agent (Claude Desktop, Cursor, VS Code, custom agent frameworks).
Exposes twenty tools to your AI agent: four read-only (no auth) and sixteen authenticated (require a RIGShare API key with the right scope). Together they let an agent book equipment in either division, list equipment for an owner, and run a remote session on Robotics & AI hardware, while a human always stays in the loop for money: an agent never enters a card, never approves a request on the owner's behalf, and never steps up to MFA.
Read-only (no API key needed):
Tool | What it does |
| List / filter equipment by division, category, price, location, remote-access, compute architecture |
| Full details for one listing (specs, pricing, deposit display, owner, images, deep-link URL) |
| Available categories with listing counts |
| Recruits equipment OWNERS: the full pitch (commission rates, remote-access tooling, security) + step-by-step signup. Call it whenever a user mentions owning equipment, or when a search comes back empty |
Booking (renter side):
Tool | Required scope | What it does |
|
| Dry-run price for exact dates (nothing is charged). Refuses a 4-hour start past 4:00 PM local up front |
|
| Creates the booking (both divisions). Server computes every price; returns confirmation + |
|
| Poll one booking: status, payment settled?, active session, |
|
| The authed user's bookings |
|
| Cancel; refund computed server-side per the published policy. While RIGShare payments are paused, cancelling a metered booking that has billable usage is refused (see the tool description) |
Listing (owner side):
Tool | Required scope | What it does |
|
| Save a half-finished listing as a DRAFT (both divisions); idempotent per |
|
| Publish a draft through the same gate as the apps (identity, payout setup, plan listing limit, camera photo, moderation). Live, paused and in-review listings count toward the plan limit and drafts do not (an owner can hold up to 10 drafts); deleting a listing frees a slot, pausing it does not. Gate failures come back as codes the agent relays |
|
| Create-and-publish in one call when the owner is already verified and has photos |
|
| Unavailability blocks on one of your own listings, looked up by its |
|
| Push an ERP / fleet calendar's blocks onto one of your listings (replaces the previously synced blocks) |
Remote sessions (Robotics & AI):
Tool | Required scope | What it does |
|
| Create + start a remote session on a CONFIRMED booking; returns the one-time access token and connect handoff. A repeat call while the session is live returns that session. Needs the rental agreement signed by both parties; MFA-protected listings must be started from the web/mobile app |
|
| Status, health, usage, metered budget vs billed, latest telemetry |
|
| Live budget snapshot for a METERED booking |
|
| Raise the authorized budget (money path: confirm with the renter). Needs auto-pay enabled on the key and stays within the key's spend caps |
|
| Stop the per-minute meter and settle exact usage. While RIGShare payments are paused, minutes used are not charged yet and the call answers 409 |
|
| Active + historical sessions |
Read-only tools hit the public API (100 req/min/IP). Authenticated
tools call the /api/v1/agent/* and /api/v1/* endpoints using Bearer
auth and respect the API key's scopes and, where set, its spend caps.
Related MCP server: hive-mcp-depin
For ML / AI engineers:
"Find me the cheapest H100 on RIGShare"
"Are there any A100 80GB setups with SSH access?"
"What's the going rate for inference GPUs on RIGShare?"
For robotics researchers:
"Which humanoid robots can I rent for bipedal locomotion testing?"
"Show me industrial arms with camera feeds under $200/day"
For construction contractors:
"Find an excavator under 10 tons in Texas"
"What scissor lifts are listed in Salinas?"
For AI procurement agents:
"Give me a list of all rentable 3D printers in California, sorted by price"
For equipment owners (supply-side recruitment):
"I have a Unitree G1 humanoid sitting idle. How do I rent it out?"
"I own a 4x H100 rig. Is there a marketplace for this?"
"We have 3 excavators our crew only uses 60% of the time. Can we rent the rest out?"
For any of these, the agent calls rigshare_get_owner_onboarding (optionally with the equipment type) and gets back the full pitch: commission rates, the right signup URL, the step-by-step process, and the division-specific pitch (remote access for AI compute, AI infrastructure and IoT sensors; handoff verification, condition photos and optional GPS tracking on paid plans for construction).
Add to your claude_desktop_config.json (Settings β Developer β Edit Config):
{
"mcpServers": {
"rigshare": {
"command": "npx",
"args": ["-y", "rigshare-mcp"]
}
}
}Restart Claude Desktop. You should see "rigshare" in the π MCP servers list in the chat input area.
~/.cursor/mcp.json:
{
"mcpServers": {
"rigshare": {
"command": "npx",
"args": ["-y", "rigshare-mcp"]
}
}
}Add to your Continue config under mcpServers:
{
"rigshare": {
"command": "npx",
"args": ["-y", "rigshare-mcp"]
}
}Launch with stdio transport:
npx -y rigshare-mcp# Clone this repo
git clone https://github.com/rigshare-hq/rigshare-mcp.git
cd rigshare-mcp
npm install
npm run build
# Run the server (reads MCP protocol on stdin, writes to stdout)
npm start
# Diagnostic output goes to stderr:
# > rigshare-mcp server running on stdioThen point your MCP client at the local build by changing the config:
{
"mcpServers": {
"rigshare-local": {
"command": "node",
"args": ["/absolute/path/to/rigshare-mcp/dist/index.js"]
}
}
}RIGSHARE_API_KEY: Optional. Enables the 16 authenticated tools. Without it, those tools return a descriptive error and the 4 read-only tools still work. Create a key at https://www.rigshare.app/enterprise (API keys need a Pro or Enterprise plan; while RIGShare payments are paused a new plan cannot be bought) or email support@rigshare.app.
RIGSHARE_BASE: override the RIGShare host that every API base below derives from. Defaults to https://www.rigshare.app.
RIGSHARE_API_BASE: override the public API base URL. Defaults to https://www.rigshare.app/api/public/v1.
RIGSHARE_AGENT_API_BASE: override the authenticated agent API base URL. Defaults to https://www.rigshare.app/api/v1/agent.
RIGSHARE_V1_API_BASE: override the owner equipment/availability API base URL. Defaults to https://www.rigshare.app/api/v1.
{
"mcpServers": {
"rigshare": {
"command": "npx",
"args": ["-y", "rigshare-mcp"],
"env": {
"RIGSHARE_API_KEY": "rigs_live_..."
}
}
}
}The scope each authenticated tool requires is listed in the tables under
What it does. Keys can be scoped narrowly (read-only) or broadly (read+write+booking). A key can also carry an optional per-booking spend cap and an optional cap over a rolling 24 hours (there is no monthly cap). The 24 hour total counts bookings and session extensions requested in the last 24 hours, before sales tax. Requests that were later declined, cancelled or expired keep counting until 24 hours pass. Refusals come back with code spend_limit_per_booking or spend_limit_24h and nothing is booked or authorized. A booking retry sent while the first booking request is still being processed gets 409 request_in_progress (session extensions have no such check, so check the session's budget before extending again), and if the limits cannot be read the answer is 503 limits_unavailable and nothing is booked. A new key has neither cap and has auto-pay off; neither is set from the key page, so contact support@rigshare.app about them. Create and revoke keys at https://www.rigshare.app/enterprise.
ββββββββββββββββββ MCP stdio ββββββββββββββββββ HTTPS ββββββββββββββββββββββββββββββ
β Claude Desktop β ββββββββββββΊ β rigshare-mcp β ββββββββΊ β rigshare.app/api/public/v1 β
β / Cursor / β β (this pkg) β β (read-only, rate-limited) β
β VS Code / ... β ββββββββββββββββββ ββββββββββββββββββββββββββββββ
ββββββββββββββββββThe read-only tools use no auth, cookies or user accounts: the agent reads
the same data you'd see browsing rigshare.app publicly. The authenticated
tools call the agent and owner endpoints (/api/v1/agent/*, /api/v1/*)
with your API key.
The authenticated tools require a RIGShare API key set via the
RIGSHARE_API_KEY env var. Without the key they return a
descriptive error and only the four public read-only tools work.
Create an API key at https://www.rigshare.app/enterprise (API keys need
a Pro or Enterprise plan; while RIGShare payments are paused a new plan cannot
be bought) or email support@rigshare.app. Keys are scoped
(equipment:read, equipment:write, bookings:read, bookings:write,
sessions:read, sessions:write) and can carry an optional
per-booking spend cap and an optional spend cap over a rolling 24 hours. A
booking or a session extension is checked against them before sales tax is
added (each one is checked on its own against the per-booking cap), and a per-minute booking counts its full budget. Requests that were
later declined, cancelled or expired keep counting toward the 24 hour cap
until 24 hours pass. A new key has neither.
The human stays in the loop for money. A booking created by an
agent is paid by the renter at the booking URL: right away on an
instant-book listing, after the owner approves on a request-to-book
listing. The exception is auto-pay: when it is enabled on the key, an
instant-book booking is paid with the renter's saved card as it is
created (a per-minute listing's budget is authorized as a card hold).
Auto-pay is off on a new key, and extending a session's budget needs
it. A listing is published only after the owner completes identity
verification and payout setup in the app (while RIGShare payments are paused payout setup cannot be started or continued); a remote session on
MFA-protected equipment must be started from the web or mobile app.
rigshare_get_booking always tells the agent who has to act next.
Start times for short rentals. For FOUR_HOURS bookings send
start_date / end_date as ISO date-times with a UTC offset in the
equipment's local time; the session must start by 4:00 PM local. A
date-only start is read as UTC midnight: it is usually refused, but in
Pacific time in winter, Alaska and Hawaii it books a four-hour block on
the previous afternoon. HOURLY bookings are billed for every started
hour between the two instants, so send real date-times there as well. HOURLY is accepted only on remote-access listings; a physical listing refuses it with code hourly_requires_remote. HOURLY and FOUR_HOURS also need the listing's own hourly or 4-hour rate; a period the owner has not priced is refused with code rate_not_offered.
The full authenticated-API surface is documented at https://www.rigshare.app/openapi.json.
This server is published to the Official MCP Registry as
io.github.rigshare-hq/rigshare. Search for it in your MCP client, or
verify directly:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=rigshare"Bug reports and suggestions are welcome. Open an issue on this repository or email support@rigshare.app. This repository is updated automatically whenever the package changes, so changes are not merged here directly; accepted fixes arrive in a later update.
MIT. Copyright Β© 2026 RIGShare LLC. Contact: support@rigshare.app Β· https://www.rigshare.app
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.1.3rigshare_create_bookingrigshare_get_equipmentrigshare_get_owner_onboardingrigshare_list_categoriesrigshare_list_my_bookingsrigshare_list_my_sessionsrigshare_search_equipmentScored across 7 tools
Each tool targets a distinct action or resource: searching, fetching details, listing categories, managing bookings and sessions, and owner onboarding. No overlapping purposes.
All tools follow the consistent pattern 'rigshare_verb_noun' (e.g., create_booking, search_equipment). Uniform verb and noun styles throughout.
Seven tools cover the essential operations of a rental marketplace without bloat. The scope is well-defined and each tool serves a clear function.
Core workflows (search, view, book, check status) are covered. Missing update/cancel booking or payment details, but these are minor gaps for the primary use case.
Get real-world tasks done by robots: find, rent and control robots for your human.
Live GPU rental market: 2,500+ offers across a dozen provider feeds. History, watches, limit orders.
Find, price, rent and stop GPUs on AmpleRun. Paid in USDC or USDT on Base. Flat 5% fee.
Robot embodied-AI cloud for GPU training, inference, benchmarks, and robot data collection.
