RH

rigshare-hq/rigshare-mcp

Developer tools

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る

0 stars 0 forks 品質 86 トレンド 14MIT

Model Context Protocol server for RIGShare — browse construction equipment and Robotics & AI hardware rentals from any MCP-compatible AI agent. Also recruits equipment owners.

概要

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 equipment in either division, equipment for an owner, and 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 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. - "Find me the cheapest H100 available this weekend" - "Are there any A100 80GB setups with SSH access right now?" - "What's the going rate for inference GPUs on RIGShare?

README

以下は原文 README の抜粋です。原文を見る。

rigshare-mcp

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).

What it does

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
rigshare_search_equipment List / filter equipment by division, category, price, location, remote-access, compute architecture
rigshare_get_equipment Full details for one listing (specs, pricing, deposit display, owner, images, deep-link URL)
rigshare_list_categories Available categories with listing counts
rigshare_get_owner_onboarding 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
rigshare_quote_booking bookings:read Dry-run price for exact dates (nothing is charged). Refuses a 4-hour start past 4:00 PM local up front
rigshare_create_booking bookings:write Creates the booking (both divisions). Server computes every price; returns confirmation + next_action (who acts next, and the URL). While RIGShare payments are paused, booking is refused and nothing is booked or charged; tell the renter and do not retry in a loop
rigshare_get_booking bookings:read Poll one booking: status, payment settled?, active session, next_action (who acts next, and the URL). Request-to-book: owner approves → renter pays at the URL → confirmed. Instant-book: the renter pays at the URL right away
rigshare_list_my_bookings bookings:read The authed user’s bookings
rigshare_cancel_booking bookings:write 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
rigshare_save_draft_listing equipment:write Save a half-finished listing as a DRAFT (both divisions); idempotent per draft_session_id (a re-save changes only the fields you pass). Include replacement_value_usd for a physical listing (caps the displayable deposit; the server may require it to publish)
GitHub で README 全文を見る

インストール

npx -y rigshare-mcp
MCP 初心者?mcpskill.org のガイドから始めましょう →

設定

{ "mcpServers": { "rigshare": { "command": "npx", "args": ["-y", "rigshare-mcp"] } } }