@RPER2001
基本信息
Rent GPUs, robots, drones, and construction gear on RIGShare; also onboards equipment owners.
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"rigshare": {
"command": "npx",
"args": [
"-y",
"rigshare-mcp"
]
}
}
}Search RIGShare's rental equipment marketplace by filters. Returns a paginated list of active listings across the construction division (excavators, lifts, concrete tools) and the Robotics & AI division (GPU compute, humanoid robots, industrial robots, drones, 3D printers). Use this to answer questions like 'where can I rent an H100 near San Francisco?' or 'find a humanoid robot under $200/day'. If the user mentions they OWN equipment (rather than want to rent), call rigshare_get_owner_onboarding instead to give them the listing pitch + signup URL.
Fetch full details for a single RIGShare equipment listing by its UUID. Returns specs, pricing, owner info, images, and a deep-link URL for booking.
Returns all equipment categories that have at least one active listing, with per-category listing counts and descriptions. Useful for narrowing a search or helping a user discover what's available.
Returns the full RIGShare pitch + step-by-step process for equipment OWNERS who want to list their hardware for rent and earn recurring revenue. Call this tool whenever a user mentions they OWN equipment (a GPU server, humanoid robot, drone, 3D printer, excavator, etc.) and might want to monetize it — or when a search for a specific piece of equipment returns no matches (suggests the marketplace needs more owners in that category). Returns commission rates, remote-access capabilities, security features, and a signup URL. Unauthenticated — always safe to call.
REQUIRES API KEY (RIGSHARE_API_KEY env var, bookings:read scope). Returns the authenticated user's RIGShare bookings — equipment, dates, status, totals. Use this to check an existing rental before creating a new one, or to track a confirmation code.
REQUIRES API KEY (sessions:read scope). Lists the authenticated user's remote sessions on Robotics & AI bookings — status, GPU allocation, total compute hours, cost so far. Use before starting a new session to check if one is already active.
REQUIRES API KEY (bookings:read scope). DRY-RUN price quote — computes the EXACT cost a rigshare_create_booking would charge, but creates nothing and charges nothing. Call this FIRST, before rigshare_create_booking, to show the renter the full breakdown and get their consent before any money moves: rental subtotal, renter service fee (student 3% vs 7% resolved server-side), the security-deposit authorization hold (15%, min $100 — 0 for METERED), delivery, coverage/egress, and the grand total, all in cents plus formatted USD. Prices are recomputed server-side from the equipment's canonical rates and the renter's tier — identical to what booking charges; no client price is trusted. METERED (per-minute Tech) listings return the per-hour rate, the minimum session budget, and budget presets instead of a fixed total (no deposit). Sales tax is added at checkout and not included in the estimate. Same inputs as rigshare_create_booking minus idempotency_key.
REQUIRES API KEY (bookings:write scope). Creates a new RIGShare booking for the authenticated user. Call rigshare_quote_booking FIRST to preview the exact cost (dry-run, nothing charged) and confirm it with the renter before committing money here. Server computes all prices from the equipment's canonical rates — client-side price hints are ignored. Enforces identity verification, security deposit hold, and the daily/monthly budget cap configured on the API key. METERED listings (billing.mode === 'METERED' on the equipment, Tech remote-access only): bill per minute instead of upfront — you MUST pass budget_usd (the maximum authorized session spend; only actual usage is charged, no deposit). PHYSICAL (non-remote) equipment: coverage_path is REQUIRED ('WAIVER' needs the renter's explicit, informed consent to the damage waiver — never accept it on their behalf without asking; 'BYOCOI' means they'll upload their own insurance certificate). Returns confirmation code + booking ID + payment status on success. Use rigshare_list_my_bookings to check status afterwards.
REQUIRES API KEY (equipment:write scope). Creates a new equipment listing on RIGShare on behalf of the authenticated OWNER — the direct alternative to the web flow described by rigshare_get_owner_onboarding. Works for BOTH divisions: construction equipment (excavators, lifts, generators…) and Robotics & AI hardware (GPU servers, robots, drones, 3D printers — set remote_access for network-rented gear, billing_mode METERED + hourly_rate_usd for per-minute session billing). Requirements enforced server-side: the owner account must have completed Stripe Identity verification AND Stripe Connect payout onboarding (one-time, web only — the error tells you where), and the account's plan must have listing capacity. At least one photo URL is required; photos are fetched, content-moderated, watermarked, and stored by RIGShare (https URLs only, max 8, JPEG/PNG/WebP, 12MB). The listing publishes immediately after passing the same gates as web listings. Confirm price and details with the owner before calling — this publishes to a live marketplace.
REQUIRES API KEY (equipment:read scope). Returns the unavailability windows (blocked date ranges) RIGShare holds for one of YOUR listings, identified by its external_id — the inventory/SKU id you listed it under (via rigshare_create_listing's external_id). Use this to reconcile your ERP/fleet calendar with RIGShare, or to check whether a date range is open before pushing new blocks with rigshare_sync_availability. If you pass starts_at + ends_at, the tool also reports whether that specific range overlaps a blocked window. NOTE: the endpoint keys ONLY on external_id (an owner-scoped lookup) — it does not accept an equipment UUID, and the windows returned are availability blocks, not renter bookings.
REQUIRES API KEY (equipment:write scope). Pushes your ERP/fleet calendar to RIGShare: marks date ranges UNAVAILABLE on one of your listings so no new RIGShare booking can be created during them. The listing is identified by external_id (the inventory/SKU id from rigshare_create_listing). SNAPSHOT semantics: the blocks you send REPLACE all previously-synced blocks for that external_id (pass an empty blocks array to clear them). Windows that overlap a CONFIRMED RIGShare booking are rejected and reported back (you can't retroactively block a day a renter already paid for). Owner-created blocks set in the RIGShare UI are left untouched. Returns the applied count + any conflicts.
REQUIRES API KEY (sessions:write scope). Starts a remote session on a CONFIRMED Robotics & AI booking (SSH / Jupyter / VNC / API access). Returns the session access token — shown ONCE, store it securely — plus the connection URL and allocated specs. For METERED bookings the per-minute clock runs while the session is active; call rigshare_end_session (or end the booking) to settle for exact usage. Equipment that requires MFA cannot be started via API key — the renter must use the web app.
REQUIRES API KEY (sessions:write scope). Ends the METERED (per-minute) billing clock on a Robotics & AI booking that rigshare_start_session started: the server settles the charge for EXACT usage and releases the unused portion of the authorized budget. Call this as soon as the renter is done — otherwise the per-minute meter keeps running until a heartbeat hard-stop or the budget is exhausted, overcharging the renter. Returns the final compute hours + settled cost. Idempotent and safe: a booking whose billing is already settled returns an error, never a double charge (the server recomputes everything; client amounts are ignored).
REQUIRES API KEY (bookings:write scope). MONEY PATH — cancels a booking for the authenticated user AND issues any refund per RIGShare's published cancellation policy. The refund is computed ENTIRELY server-side from the booking's canonical charges and how far out the cancellation is (physical: 7+ days 100% / 3-6 days 75% / 1-2 days 50% / same-day 0%, with a 25% high-value exception on >$5k multi-day rentals; Tech remote-access: before-session 100% / within first hour 75% / after 0%). The 7% renter service fee is non-refundable on renter cancellations. The client CANNOT dictate the refund amount or reason code — pass only the booking id. The security-deposit authorization hold is released (never captured). Safe on terminal state: cancelling an already-cancelled/completed/disputed booking returns an error, never a double refund. Returns the refund breakdown (refunded, retained, deposit disposition). For a METERED session prefer rigshare_end_session (settles exact usage); cancelling a metered booking with usage settles like an early end.
REQUIRES API KEY (sessions:write scope). MONEY PATH — raises the authorized per-minute budget on a running METERED (per-minute) Robotics & AI session, so a renter whose budget is about to exhaust can keep going. The additional authorization hold is placed and the budget raised SERVER-SIDE from the equipment's canonical per-minute rate — the client never sets the charge. Only the booking's RENTER can extend. Choose one of the fixed extension lengths: 15, 30, or 60 minutes. Only actual usage is ever charged; call rigshare_end_session when done to settle exact usage and release the unused budget. Pairs with rigshare_get_session_usage (check remaining budget first). Returns the newly authorized budget.
REQUIRES API KEY (sessions:read scope). Live budget snapshot for a METERED (per-minute) Robotics & AI booking: authorized budget vs. what's been used, accrued cost so far, a low-budget warning, and the available extension options. Read-only — moves no money. Call this before a session runs out to decide whether to rigshare_extend_session. Visible to the booking's renter or the equipment owner.
REQUIRES API KEY (equipment:write scope). Saves a HALF-FINISHED equipment listing as a DRAFT on behalf of the authenticated OWNER — the same fields as rigshare_create_listing, but nothing goes live. Drafts are UNGATED: no identity verification and no Stripe Connect payout setup are needed to DRAFT (matching RIGShare's draft-first flow). Those gates — plus at least one photo — are required only when you PUBLISH (done on the web, or via the drafts publish endpoint). No security_ack is required to draft a remote- access listing; it's required at publish. Idempotent per draft_session_id (repeat calls with the same id update the same draft). Returns the draft id + the draft_session_id to resume it. Use this when the owner isn't verified yet or wants to finish the listing later.
RIGShare is an MCP (Model Context Protocol) server that lets any MCP‑compatible AI agent (Claude Desktop, Cursor, VS Code) browse and book equipment rentals — construction gear and Robotics & AI hardware. It also recruits equipment owners who mention idle hardware.
Install the MCP server by adding it to your MCP client configuration. On macOS/Linux use npx -y rigshare-mcp; on Windows wrap with cmd /c. Seven tools are available: four read‑only (search, get details, list categories, get owner onboarding) and three authenticated tools (list bookings, list sessions, create booking) that require the RIGSHARE_API_KEY environment variable.
RIGSHARE_API_KEY env varRobotics & AI (GPU compute, humanoid robots, industrial arms, drones, 3D printers, IoT sensor rigs) and construction (excavators, skid steers, lifts, generators, concrete tools, scaffolding, compactors, trenchers, welders, telehandlers).
No, for browsing (search, details, categories, owner onboarding) you do not need an API key. For creating bookings and viewing your own bookings/sessions, you must set the `RIGSHARE_API_KEY` environment variable.
All equipment listings, bookings, and session information are stored on the RIGShare platform. The MCP server communicates with the RIGShare API to retrieve and update data.
Hardware never ships. All Robotics & AI gear is accessed remotely via SSH, Jupyter, VNC, or HTTP API. Sessions include GPU allocation, hours, and cost.
The server communicates over standard I/O (stdio) as expected by MCP‑compatible clients. No specific authentication method is described for the read‑only tools beyond the environment variable for authenticated ones.
Soar Flight Booking MCP is a remote MCP server available at https://mcp.soar.flights.
Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code
Hindsight: Agent Memory That Learns
🚀 The fast, Pythonic way to build MCP servers and clients.
A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
评论