Skip to main content
Glama

rigshare-mcp

RIGShare 的模型上下文协议 (MCP) 服务器 — 可从任何兼容 MCP 的 AI 代理(Claude Desktop、Cursor、VS Code、自定义代理框架)中浏览建筑设备以及机器人与 AI 硬件租赁信息。

功能介绍

向您的 AI 代理公开七个工具 — 其中四个为只读(无需身份验证),三个为已验证(需要 RIGShare API 密钥)。

只读(无需 API 密钥):

工具

功能

rigshare_search_equipment

按部门、类别、价格、位置、远程访问权限列出/筛选设备

rigshare_get_equipment

获取单个列表的详细信息(规格、定价、所有者、图片、深度链接 URL)

rigshare_list_categories

查看带有列表数量的可用类别

rigshare_get_owner_onboarding

招募设备所有者 — 返回完整的推介信息(佣金率、远程访问工具、安全功能)以及分步注册说明。当用户提到他们拥有想要出租的设备,或者搜索结果为空(表明市场在该类别中需要所有者)时,请调用此工具。

已验证(需要具有适当作用域的 RIGSHARE_API_KEY 环境变量):

工具

所需作用域

功能

rigshare_list_my_bookings

bookings:read

已验证用户的 RIGShare 预订信息 — 设备、日期、状态、总计

rigshare_list_my_sessions

sessions:read

活动及历史远程会话(GPU 分配、时长、成本)

rigshare_create_booking

bookings:write

创建新预订。服务器计算价格;客户端提示将被忽略。强制执行身份验证、保证金扣留和每个密钥的预算上限

只读工具访问公共 API(每 IP 每分钟 100 次请求)。已验证工具使用 Bearer 身份验证访问 /api/v1/agent/* 接口,并遵循 API 密钥配置的作用域和预算上限。

Related MCP server: hive-mcp-depin

使用场景

针对 ML / AI 工程师:

  • “帮我找到本周末可用的最便宜的 H100”

  • “现在有带 SSH 访问权限的 A100 80GB 设置吗?”

  • “RIGShare 上推理 GPU 的当前费率是多少?”

针对机器人研究人员:

  • “我能租到哪些人形机器人用于双足运动测试?”

  • “向我展示每天 200 美元以下的带摄像头馈送的工业机械臂”

针对建筑承包商:

  • “在德克萨斯州找一台 10 吨以下的挖掘机”

  • “本周萨利纳斯有哪些剪叉式升降机可用?”

针对 AI 采购代理:

  • “给我一份加利福尼亚州所有可租赁 3D 打印机的列表,按价格排序”

针对设备所有者(供应端招募):

  • “我有一台闲置的 Unitree G1 人形机器人 — 我该如何出租它?”

  • “我拥有一台 4x H100 矿机 — 有相关的市场吗?”

  • “我们有 3 台挖掘机,但我们的团队只有 60% 的时间在使用它们。我们可以把剩下的时间出租出去吗?”

对于以上任何情况,代理都会调用 rigshare_get_owner_onboarding(可选择带上设备类型),并获得完整的推介信息:佣金率、正确的注册 URL、分步流程以及针对特定部门的推介(针对机器人/AI 的远程访问,针对建筑的 GPS + 保险)。

安装

Claude Desktop

添加到您的 claude_desktop_config.json(设置 → 开发者 → 编辑配置):

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

重启 Claude Desktop。您应该会在聊天输入区域的 🔌 MCP 服务器列表中看到“rigshare”。

Cursor

~/.cursor/mcp.json:

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

VS Code (Continue 扩展)

在您的 Continue 配置中的 mcpServers 下添加:

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

任何兼容 MCP 的代理框架

使用 stdio 传输启动:

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

然后通过更改配置将您的 MCP 客户端指向本地构建:

{
  "mcpServers": {
    "rigshare-local": {
      "command": "node",
      "args": ["/absolute/path/to/rigshare-mcp/dist/index.js"]
    }
  }
}

环境变量

  • RIGSHARE_API_KEY — 可选。启用已验证工具(list_my_bookings、list_my_sessions、create_booking)。如果没有它,这些工具将返回描述性错误。请在 https://www.rigshare.app/profile#api-keys 获取密钥,或发送电子邮件至 support@rigshare.app。

  • RIGSHARE_API_BASE — 覆盖公共 API 基础 URL。默认为 https://www.rigshare.app/api/public/v1。适用于暂存环境或本地开发。

  • RIGSHARE_AGENT_API_BASE — 覆盖已验证代理 API 基础 URL。默认为 https://www.rigshare.app/api/v1/agent。

带 API 密钥的 Claude Desktop 配置

{
  "mcpServers": {
    "rigshare": {
      "command": "npx",
      "args": ["-y", "rigshare-mcp"],
      "env": {
        "RIGSHARE_API_KEY": "rigs_live_..."
      }
    }
  }
}

每个已验证工具所需的作用域:

工具

最低作用域

rigshare_list_my_bookings

bookings:read

rigshare_list_my_sessions

sessions:read

rigshare_create_booking

bookings:write

密钥可以进行窄作用域(只读)或宽作用域(读+写+预订)设置,并且您可以设置每个密钥的每日/每月预算上限。请在 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 / ... │              └────────────────┘          └────────────────────────────┘
└────────────────┘

无身份验证、无 Cookie、无用户账户 — 代理读取的数据与您在 rigshare.app 上公开浏览时看到的数据相同。

写入操作

三个已验证工具(rigshare_list_my_bookings、rigshare_list_my_sessions、rigshare_create_booking)需要通过 RIGSHARE_API_KEY 环境变量设置 RIGShare API 密钥。如果没有密钥,这些工具将返回描述性错误,且只有四个公共只读工具可以使用。

请在 https://www.rigshare.app/profile#api-keys 获取 API 密钥,或发送电子邮件至 support@rigshare.app。密钥具有作用域(bookings:read、bookings:write、sessions:read、sessions:write)并带有可配置的每日/每月预算上限。

完整的已验证 API 接口文档请见 https://www.rigshare.app/openapi.json。

注册列表

此服务器已作为 io.github.RPER2001/rigshare 发布到 官方 MCP 注册表。请在您的 MCP 客户端中搜索它,或直接验证:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=rigshare"

贡献

欢迎提交错误报告和 PR。此公共仓库镜像了 RIGShare 主单体仓库(商业市场代码保持私有)的 MCP 服务器部分。更改会从单体仓库流向此仓库;对于紧急修复,您也可以直接在此处提交 PR。

许可证

MIT。版权所有 © 2026 RIGShare LLC。 联系方式:support@rigshare.app · https://www.rigshare.app

Available Tools

7 tools
rigshare_create_bookingA

REQUIRES API KEY (bookings:write scope). Creates a new RIGShare booking for the authenticated user. Server computes all prices from the equipment's canonical rates — client-side price hints are ignored. Enforces identity verification, security deposit hold, and a daily/monthly budget cap configured on the API key. Returns confirmation code + booking ID on success. Use rigshare_list_my_bookings to check status afterwards.

Inputs: equipment_id (required), start_date (required), end_date (required), duration_type (required), +2 more.

rigshare_get_equipmentA

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.

Inputs: id (required).

rigshare_get_owner_onboardingA

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.

Inputs: equipment_type, division_hint.

rigshare_list_categoriesA

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.

Inputs: no named parameters.

rigshare_list_my_bookingsA

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.

Inputs: status, limit, page.

rigshare_list_my_sessionsA

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.

Inputs: booking_id, status.

rigshare_search_equipmentA

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.

Inputs: division, category, remote_only, access_type, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: searching, fetching details, listing categories, managing bookings and sessions, and owner onboarding. No overlapping purposes.

    Naming Consistency5/5

    All tools follow the consistent pattern 'rigshare_verb_noun' (e.g., create_booking, search_equipment). Uniform verb and noun styles throughout.

    Tool Count5/5

    Seven tools cover the essential operations of a rental marketplace without bloat. The scope is well-defined and each tool serves a clear function.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers