Server data from the Official MCP Registry
Rent GPUs, robots, drones, and construction gear on RIGShare; also onboards equipment owners.
Rent GPUs, robots, drones, and construction gear on RIGShare; also onboards equipment owners.
This is a well-architected MCP server with proper authentication controls, clear permission boundaries, and secure credential handling. The code properly gates authenticated operations behind API key checks, uses environment variables for secrets, and makes appropriate API calls without exfiltration risks. Minor code quality observations exist but do not materially impact security. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
3 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: RIGSHARE_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-rper2001-rigshare": {
"env": {
"RIGSHARE_API_KEY": "your-rigshare-api-key-here"
},
"args": [
"-y",
"rigshare-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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 seven tools to your AI agent — four read-only (no auth) and three authenticated (require a RIGShare API key).
Read-only (no API key needed):
| Tool | What it does |
|---|---|
rigshare_search_equipment | List / filter equipment by division, category, price, location, remote-access |
rigshare_get_equipment | Full details for one listing (specs, pricing, owner, images, deep-link URL) |
rigshare_list_categories | Available categories with listing counts |
rigshare_get_owner_onboarding | Recruits equipment OWNERS — returns the full pitch (commission rates, remote-access tooling, security features) + step-by-step signup instructions. Call this whenever a user mentions they OWN equipment they'd like to rent out, OR when a search returns empty (signal that the marketplace needs owners in that category). |
Authenticated (require RIGSHARE_API_KEY env var with appropriate scopes):
| Tool | Required scope | What it does |
|---|---|---|
rigshare_list_my_bookings | bookings:read | The authed user's RIGShare bookings — equipment, dates, status, totals |
rigshare_list_my_sessions | sessions:read | Active + historical remote sessions (GPU alloc, hours, cost) |
rigshare_create_booking | bookings:write | Create a new booking. Server computes prices; client hints are ignored. Enforces ID verification, security deposit hold, and per-key budget caps |
Read-only tools hit the public API (100 req/min/IP). Authenticated
tools hit the /api/v1/agent/* surface using Bearer auth and
respect the API key's configured scopes + budget caps.
For ML / AI engineers:
For robotics researchers:
For construction contractors:
For AI procurement agents:
For equipment owners (supply-side recruitment):
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 robotics/AI, GPS + insurance 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/RPER2001/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 stdio
Then 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 authenticated tools (list_my_bookings, list_my_sessions, create_booking). Without it, those tools return a descriptive error. Get a key at https://www.rigshare.app/profile#api-keys or email support@rigshare.app.RIGSHARE_API_BASE — override the public API base URL. Defaults to https://www.rigshare.app/api/public/v1. Useful for staging or local development.RIGSHARE_AGENT_API_BASE — override the authenticated agent API base URL. Defaults to https://www.rigshare.app/api/v1/agent.{
"mcpServers": {
"rigshare": {
"command": "npx",
"args": ["-y", "rigshare-mcp"],
"env": {
"RIGSHARE_API_KEY": "rigsk_live_..."
}
}
}
}
Scopes required for each authenticated tool:
| Tool | Minimum scope |
|---|---|
rigshare_list_my_bookings | bookings:read |
rigshare_list_my_sessions | sessions:read |
rigshare_create_booking | bookings:write |
Keys can be scoped narrowly (read-only) or broadly (read+write+booking), and you can set per-key daily/monthly budget caps. Manage at https://www.rigshare.app/profile#api-keys.
┌────────────────┐ MCP stdio ┌────────────────┐ HTTPS ┌────────────────────────────┐
│ Claude Desktop │ ◄──────────► │ rigshare-mcp │ ───────► │ rigshare.app/api/public/v1 │
│ / Cursor / │ │ (this pkg) │ │ (read-only, rate-limited) │
│ VS Code / ... │ └────────────────┘ └────────────────────────────┘
└────────────────┘
No auth, no cookies, no user accounts — the agent reads the same data you'd see browsing rigshare.app publicly.
The three authenticated tools (rigshare_list_my_bookings,
rigshare_list_my_sessions, rigshare_create_booking) require a
RIGShare API key set via the RIGSHARE_API_KEY env var. Without
the key, those tools return a descriptive error and only the four
public read-only tools work.
Get an API key at https://www.rigshare.app/profile#api-keys or
email support@rigshare.app. Keys are scoped (bookings:read,
bookings:write, sessions:read, sessions:write) and carry
configurable daily / monthly budget caps.
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.RPER2001/rigshare. Search for it in your MCP client, or
verify directly:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=rigshare"
Bug reports + PRs welcome. This public repo mirrors the MCP-server portion of the main RIGShare monorepo (which stays private for the commercial marketplace code). Changes flow from the monorepo → this repo on each release; for hot fixes you can also PR directly here.
MIT. Copyright © 2026 RIGShare LLC. Contact: support@rigshare.app · https://www.rigshare.app
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.