Skip to content

The construction procurement MCP connector

Run Vadiy from Claude, Codex, or ChatGPT.

Everything your team does on the site, your AI tools can now do with you: ask about orders, projects, deliveries, RFIs, and invoices, or take real actions like submitting and approving material orders. Every call runs with your own login's permissions, and every action lands in the same audit trail as a click on the site.

Things you can just say

  • What orders are waiting on me to approve?
  • Submit an order to SSP1: 40 ft of 3/4 EMT and 2 boxes of wire nuts, needed Friday, deliver to the warehouse.
  • Why is order MAPLE-2-003 stuck? Show me its timeline.
  • What did we last pay for 5/8 ground rods?
  • Open an RFI on KIPP-DOOR: the door schedule conflicts with sheet A-401.
  • Which invoices are still unpaid this month?
  • Where is my hammer drill? Ask whoever has it to send it back.

How it works

  1. Sign in and open https://vadiy.com/account/connectors.
  2. Create a personal access token (you can revoke it any time; we store only its fingerprint).
  3. Paste the ready-made setup for your tool below. Done: ask a question or give an instruction.

Works with the tools you already use

claude.ai

Settings, then Connectors, then Add custom connector. Paste your tokenized URL:

https://vadiy.com/api/mcp/mcp?key=vadiy_pat_YOUR_TOKEN
Claude Code

One command in your terminal:

claude mcp add --transport http vadiy https://vadiy.com/api/mcp/mcp --header "Authorization: Bearer vadiy_pat_YOUR_TOKEN"
Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.vadiy]
command = "npx"
args = ["-y", "mcp-remote", "https://vadiy.com/api/mcp/mcp", "--header", "Authorization: Bearer vadiy_pat_YOUR_TOKEN"]
ChatGPT

Settings, then Connectors (developer mode), then add the same tokenized URL:

https://vadiy.com/api/mcp/mcp?key=vadiy_pat_YOUR_TOKEN

Built like the rest of Vadiy

  • A token carries exactly your role. A foreman's AI can submit orders but never approve them or see a price; the database refuses, not the interface.
  • Every action is written to the audit log in plain English with a timestamp.
  • Tokens are shown once, stored as fingerprints, and revocable in one click.