Pipeyard

MCP开发工具

提供方 未标注

开发工具 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

为行业垂直领域精心策划的MCP连接器市场——涵盖建筑、金融、医疗和物流,提供完整文档、curl示例及沙盒测试。

一句话选型结论

按资料字段整理

Pipeyard 属于开发工具类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

开发

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Pipeyard当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.9 KB
来自项目仓库与上游目录的原文,未做删改

Procore MCP Server

This project implements a Model Context Protocol (MCP) server that connects Claude (and other MCP‑aware clients) to the Procore API. It exposes tools for working with:

  • Projects
  • RFIs
  • Submittals
  • Documents
  • Budget & cost

All tools return clean JSON responses, validate inputs with zod, and include robust error handling for 401, 403, 404, and 429 (rate limit) responses from Procore.


Prerequisites

  • Node.js: v18+ (recommended)
  • npm: v9+ (comes with recent Node.js)
  • Procore Developer account with:
  • A registered OAuth2 client using Client Credentials flow
  • API access to the relevant projects/modules (RFIs, Submittals, Documents, Budget, etc.)

Installation```bash

cd C:\Procore
npm install


If you created the folder elsewhere, adjust the `cd` path accordingly.

---

### Getting Procore API credentials

- Go to the Procore Developer Portal.
- Create an **OAuth Client** using the **Client Credentials** grant type.
- Note the following values:
  - **Client ID**
  - **Client Secret**
- Ensure the client has **access scopes** appropriate for:
  - Projects
  - RFIs
  - Submittals
  - Documents
  - Budget & cost management

You will use these values in your `.env` file.

---

### Environment variable setup

Create a `.env` file in the project root (next to `package.json`) based on `.env.example`:```bash
cp .env.example .env

Then edit .env:```bash
PROCORE_CLIENT_ID=your_real_client_id
PROCORE_CLIENT_SECRET=your_real_client_secret
PROCORE_BASE_URL=https://api.procore.com


- **PROCORE_CLIENT_ID**: From the Procore developer portal.
- **PROCORE_CLIENT_SECRET**: From the Procore developer portal.
- **PROCORE_BASE_URL**: Typically `https://api.procore.com` (you can override for sandbox/test environments).

---

### Build and run locally

Install dependencies:```bash
npm install

Run in development mode (TypeScript via tsx):```bash
npm run dev


Build TypeScript to `dist/`:```bash
npm run build

Run the compiled server:```bash
npm start


The MCP server uses **stdio** (standard input/output), so it is normally launched and managed by an MCP client such as Claude Desktop. You generally do **not** call it directly in a terminal except for debugging.

---

### Available tools

All tools return **JSON**. Arguments shown below are the **tool arguments**, not raw HTTP calls.

- **Projects**
  - **`list_projects`**
    - **Description**: List Procore projects for the authenticated client, optionally filtered by `company_id`.
    - **Inputs**:
      - `company_id` (optional, integer): Filter projects by company.
  - **`get_project`**
    - **Description**: Get details of a single project by ID.
    - **Inputs**:
      - `id` (required, integer): Project ID.

- **RFIs**
  - **`list_rfis`**
    - **Description**: List RFIs for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
  - **`get_rfi`**
    - **Description**: Get a single RFI by ID for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
      - `id` (required, integer): RFI ID.
  - **`create_rfi`**
    - **Description**: Create a new RFI in a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
      - `payload` (required, object): Raw JSON payload matching Procore’s **create RFI** API body.

- **Submittals**
  - **`list_submittals`**
    - **Description**: List submittals for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
  - **`get_submittal`**
    - **Description**: Get a single submittal by ID for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
      - `id` (required, integer): Submittal ID.
  - **`create_submittal`**
    - **Description**: Create a new submittal in a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
      - `payload` (required, object): Raw JSON payload matching Procore’s **create Submittal** API body.

- **Documents**
  - **`list_folders`**
    - **Description**: List document folders for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
  - **`list_files`**
    - **Description**: List document files for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.

- **Budget**
  - **`list_budget_line_items`**
    - **Description**: List budget line items for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.
  - **`get_budget_summary`**
    - **Description**: Get overall budget summary for a project.
    - **Inputs**:
      - `project_id` (required, integer): Project ID.

---

### Example curl-style tool calls (via MCP JSON-RPC)

MCP servers speak **JSON-RPC over stdio**; you normally don’t call them directly with curl. These examples illustrate the **payload structure** a client like Claude Desktop would send.

Replace `123` / `456` etc. with your real IDs.

- **List projects**```bash
echo '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_projects",
    "arguments": {
      "company_id": 123
    }
  }
}' | node dist/index.js
  • Get a project```bash
    echo '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
    "name": "get_project",
    "arguments": {
    "id": 123
    }
    }
    }' | node dist/index.js

- **List RFIs**```bash
echo '{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "list_rfis",
    "arguments": {
      "project_id": 123
    }
  }
}' | node dist/index.js
  • Create RFI```bash
    echo '{
    "jsonrpc": "2.0",
    "id": 4,
    "method": "tools/call",
    "params": {
    "name": "create_rfi",
    "arguments": {
    "project_id": 123,
    "payload": {
    "subject": "RFI subject here",
    "question": "Describe the question...",
    "responsible_contractor_id": 456
    }
    }
    }
    }' | node dist/index.js

- **List submittals**```bash
echo '{
  "jsonrpc": "2.0",
  "id": 5,
  "method": "tools/call",
  "params": {
    "name": "list_submittals",
    "arguments": {
      "project_id": 123
    }
  }
}' | node dist/index.js
  • Create submittal```bash
    echo '{
    "jsonrpc": "2.0",
    "id": 6,
    "method": "tools/call",
    "params": {
    "name": "create_submittal",
    "arguments": {
    "project_id": 123,
    "payload": {
    "subject": "Submittal subject",
    "spec_section": "01 30 00",
    "responsible_contractor_id": 456
    }
    }
    }
    }' | node dist/index.js

- **List folders**```bash
echo '{
  "jsonrpc": "2.0",
  "id": 7,
  "method": "tools/call",
  "params": {
    "name": "list_folders",
    "arguments": {
      "project_id": 123
    }
  }
}' | node dist/index.js
  • List files```bash
    echo '{
    "jsonrpc": "2.0",
    "id": 8,
    "method": "tools/call",
    "params": {
    "name": "list_files",
    "arguments": {
    "project_id": 123
    }
    }
    }' | node dist/index.js

- **List budget line items**```bash
echo '{
  "jsonrpc": "2.0",
  "id": 9,
  "method": "tools/call",
  "params": {
    "name": "list_budget_line_items",
    "arguments": {
      "project_id": 123
    }
  }
}' | node dist/index.js
  • Get budget summary```bash
    echo '{
    "jsonrpc": "2.0",
    "id": 10,
    "method": "tools/call",
    "params": {
    "name": "get_budget_summary",
    "arguments": {
    "project_id": 123
    }
    }
    }' | node dist/index.js

---

### Error handling behavior

All tools include consistent JSON error responses. Typical shape:```json
{
  "error": "unauthorized",
  "message": "Procore API returned 401 Unauthorized.",
  "status": 401,
  "statusText": "Unauthorized",
  "url": "/rest/v1.0/projects",
  "method": "get",
  "data": { /* raw Procore response body, if any */ }
}

Handled HTTP statuses:

  • 401: unauthorized
  • 403: forbidden
  • 404: not_found
  • 429: rate_limited
  • Other 4xx/5xx: procore_api_error
  • Validation / other errors: tool_error

How to connect to Claude Desktop (MCP config)

In Claude Desktop, add a new MCP server configuration in your claude_desktop_config.json (path may vary by OS).

Example entry:json { "mcp_servers": { "procore": { "command": "node", "args": [ "C:/Procore/procore-mcp-server/dist/index.js" ], "env": { "PROCORE_CLIENT_ID": "your_real_client_id", "PROCORE_CLIENT_SECRET": "your_real_client_secret", "PROCORE_BASE_URL": "https://api.procore.com" } } } }

  • command: node (or an explicit path to your Node binary).
  • args: Path to the compiled index.js in dist/.
  • env: You can either:
  • Inline your secrets here (be cautious), or
  • Omit env so that Claude Desktop inherits your system environment variables.

After saving the config, restart Claude Desktop. The procore MCP server should appear as an available toolset, and the tools listed above (list_projects, get_project, list_rfis, etc.) will be callable directly from within Claude.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Pipeyard 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Pipeyard 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Pipeyard 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Pipeyard 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Pipeyard 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Pipeyard 能提供哪些能力?

资料显示能力标签包括 开发。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。