Connect Claude and Codex to Vadiy
This page is for developers and power users. By the end, your AI tool is connected to Vadiy and works with exactly your permissions. It runs on MCP (the plug standard AI tools use to connect to apps). Setup takes about 2 minutes.
What you can do
- Ask questions: open orders, project status, price history, unpaid invoices, and RFIs (requests for information, formal project questions).
- Take actions: submit a material order, approve or decline one, open an RFI, add notes and comments, or configure future-order routing when your role allows it.
- Everything runs with your own permissions only. Your AI can do what you can do on the site, and nothing more.
Get a token
- Sign in and open Connect AI in the menu.
- Tap Create token. The token is shown once, so copy it right away. We store only its fingerprint and cannot show it again.
- Lost it? Revoke it and create a new one. That takes about 30 seconds.
Set up your tool
Pick your tool and paste the matching setup. Replace vadiy_pat_YOUR_TOKEN with the token you just copied.
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
The tools
Your AI sees only the tools allowed for your role. This table highlights common tools; the live connector advertises the complete role-scoped catalog.
| Tool | What it does |
|---|---|
| whoami | Your display name, organization, and roles. Call it first. |
| list_projects | The projects you can access, with their codes. |
| project_summary | One project at a glance: open orders and open RFIs. |
| list_orders | Material orders you can see, newest first, with filters. |
| get_order | One order in full, including its plain-English timeline. |
| submit_order | Submit a material order, exactly like the site's order form. |
| approve_order | Approve an order into the next step required by its saved workflow. |
| decline_order | Decline a pending order back to the foreman with a reason. |
| complete_order_without_purchase | Procurement: mark an order complete when no purchase is needed. |
| add_order_comment | Add a comment to an order's discussion thread. |
| catalog_search | Search the material catalog. Typo tolerant. |
| price_stats | Price history for one catalog item. Money roles only. |
| list_rfis | A project's RFIs with status and who owes the answer. |
| create_rfi | Open an RFI on a project. |
| answer_rfi | Answer an open RFI. The answer is stamped. |
| list_service_tickets | Service tickets with status, priority, and schedule. |
| get_service_ticket | One ticket in full: header, notes, and visits. |
| create_service_ticket | Create a service ticket. Service desk roles only. |
| add_ticket_note | Add a note to a service ticket's thread. |
| list_invoices | Service invoices. Money roles only. |
| get_invoice | One invoice with lines and payments. Money roles only. |
| service_pnl | Service department P&L: assumptions plus the 6-month table. Money roles only. |
| find_tool | Find a tool and answer where it is, who has it, and since when. |
| list_my_tools | The tools checked out to me right now. |
| request_tool_return | Ask the holder to send a tool back or confirm they have it. |
| list_people | The org directory: names, titles, phones, emails, who is away. |
| update_my_profile | Update your own phone, title, about, or away period. |
| list_schedule | A project's Gantt board: tasks, dates, assignees, milestones. |
| add_schedule_task | Put a task on the schedule. PM, service manager, or admin. |
| move_schedule_task | Slide a task by days, keeping its length. |
| assign_schedule_task | Put a person on a task, or take them off. |
| get_workflow_settings | Read your organization's routing mode, gates, and milestones. |
| set_workflow_settings | Admin: set future-order routing without changing product access or pricing. |
| get_organization_workflow_settings | Platform owner: read one organization's workflow settings by slug. |
| set_organization_workflow_settings | Platform owner: set one organization's future-order routing by slug. |
| set_org_feature | Platform owner: confirm a catalog feature is included for one organization. Disabling is refused. |
| apply_org_package | Platform owner: record a company-size pricing band without changing product access. |
| list_agent_actions | Admin only: the registry of every server-enforced action. |
Safety
- A token carries exactly your role. A foreman's token can submit orders but never approve one or see a price.
- The database refuses what your role cannot do. The rule lives on the server, not in a hidden button.
- Revoke any token at any time under Connect AI. It stops working right away.
- Every action lands in the audit trail with a timestamp, the same as a click on the site.
Planned
A REST API is planned. It does not exist yet. Today, MCP is the one way to connect a tool to Vadiy.
What next: Getting started explains roles and account setup. For the office shows the desk work your AI can help with.