Rigshare

What rigshare MCP server does

The rigshare MCP server exposes RIGShare marketplace operations through the Model Context Protocol. Agents can search listings, inspect equipment details, view categories, and retrieve owner onboarding information without an API key. The onboarding tool is intended for users who want to rent out equipment, including robotics, AI hardware, and construction machinery.

With a suitable API key, the server also supports renter, owner, and remote-session workflows. Renters can request quotes, create or cancel bookings, and check booking status. Equipment owners can save drafts, publish listings, inspect availability, and synchronize blocked dates from an external fleet or ERP calendar. For Robotics & AI rentals, agents can start, inspect, extend, and end remote sessions.

How it works

The package runs as an MCP process over standard input and output. An MCP client sends tool calls to the local process, which then communicates with RIGShare over HTTPS. Read-only calls use the public API, while authenticated calls use RIGShare API endpoints with Bearer authentication.

Four tools work without credentials and are subject to a public rate limit of 100 requests per minute per IP. Authenticated tools require a key with the scope assigned to the requested operation. Keys may also have transaction and daily spending limits.

The service keeps people involved in financial and security-sensitive actions. An agent does not enter card details, approve a request for an owner, or complete MFA. Booking responses identify the next actor and provide the relevant URL. Starting a remote session requires a confirmed booking and a rental agreement signed by both parties; MFA-protected listings must be started through the web or mobile application.

Setup and configuration

For a packaged installation, configure the MCP client to run npx -y rigshare-mcp. The README provides configurations for Claude Desktop, Cursor, and VS Code with the Continue extension. Any MCP-compatible framework can launch the same stdio command.

RIGSHARE_API_KEY is optional. Without it, the four public tools remain available while authenticated tools return an explanatory error. API keys are available through RIGShare enterprise account channels and require a Pro or Enterprise plan. The server also accepts RIGSHARE_BASE, RIGSHARE_API_BASE, RIGSHARE_AGENT_API_BASE, and RIGSHARE_V1_API_BASE to override its default host and API endpoints.

For local development, clone the repository, install dependencies with npm install, build with npm run build, and start it with npm start. A client can then point to the generated dist/index.js file.

Tools and capabilities

The rigshare MCP server groups its twenty tools into four functional areas:

• Discovery: search and filter equipment, retrieve full listing details, list categories, and explain owner onboarding.
• Bookings: quote exact dates, create or cancel bookings, list a user's bookings, and poll booking state.
• Listings: save draft equipment, publish or create listings, check availability, and replace synchronized availability blocks.
• Remote sessions: start and end sessions, inspect health and telemetry, review metered usage, extend authorized budgets, and list session history.

The server calculates booking prices and cancellation refunds on the RIGShare side. Session extension requires auto-pay on the API key and remains subject to its spending caps.

Limitations and notes

Authenticated capabilities depend on both the API key and its scopes, including bookings:read, bookings:write, equipment:read, equipment:write, sessions:read, and sessions:write. A key may be deliberately restricted to read-only operations.

Remote-session features apply to Robotics & AI hardware and require the relevant booking, signatures, and session permissions. A repeated start request while a session is live returns that session rather than creating another one. Financial actions still require the renter or owner to follow the returned handoff, approval, payment, or verification step.