Procurify MCP connector
Connecting Procurify to Elaichi lets Claude, ChatGPT, Cursor, and the Elaichi Agent look up and maintain vendors, departments, locations, account codes, and users in Procurify, with each person signed in as themselves and every action logged.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Procurify to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Procurify once
-
Open Connections, choose Add connection, and pick Procurify.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Procurify app credentials. Procurify authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Procurify MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Procurify MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Procurify MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Procurify to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Procurify through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Procurement
Set up a vendor before the first order
Add a new supplier to Procurify as soon as the quote is accepted, so the first purchase request has a vendor to point at. Ask for the vendor by name afterward to confirm it landed correctly.
-
Procurement
Clean up stale or duplicate vendor records
Pull the full vendor list from Procurify, spot the duplicates and the ones nobody has ordered from, and update or correct them in one pass instead of clicking through each record.
-
Finance
Keep account codes matching the ledger
When the chart of accounts changes, list the account codes in Procurify, add the new ones, and rename the old ones so every request is coded the way the books expect.
-
Finance
Check accounts and currencies before month end
Review which accounts and currencies are set up in Procurify so that spend in a new region or a new entity can be coded and converted without a last-minute fix.
-
Operations
Add a location when a site opens
Create the new office or warehouse as a location in Procurify and set up the departments that will order from it, so staff there can raise requests on day one.
-
IT
Onboard a new approver without a ticket
Create the person as a Procurify user, put them in the right department, and check which permission group they belong to, all from the same place you handle the rest of their setup.
Try asking
- “List every vendor in Procurify added this quarter”
- “Add a vendor called Northwind Office Supply to Procurify”
- “Which Procurify departments belong to the Austin location?”
Compare
Elaichi vs Zapier MCP vs Composio for Procurify
All three can connect Procurify to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Procurify tools | Allow or restrict single Procurify tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Procurify call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Procurify tools for your AI agents
53 tools are ready to call through Elaichi's MCP endpoint the moment you connect Procurify, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Procurify gets you
6 screens from the product, each doing one job for your Procurify account.
The agent
Ask about Procurify vendors in plain language.
Get answers from live Procurify vendors, departments, and account codes, with no report to run.
- vendors
- users
- departments
- locations
Ask Elaichi to work across your apps.
List every vendor in Procurify added this quarter
Add a vendor called Northwind Office Supply to Procurify
Which Procurify departments belong to the Austin location?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Procurify to every client.
Claude, ChatGPT, and Cursor reach Procurify through one governed endpoint, no SDK or shared key.
Copy the endpoint
Tool catalog
53 Procurify tools, no custom code.
Vendors, users, locations, departments, account codes, and currencies are covered out of the box.
- List all Procurify users
- Create a Procurify user
- Update a Procurify user by ID
- Delete a Procurify user by ID
Toolboxes
Each team gets its own Procurify toolbox.
Procurement, Finance, and Operations each see only the Procurify tools their work needs.
- Procurement
- Finance
- Accounts Payable
- Operations
Shared connections
Share a Procurify connection, never a credential.
One person connects Procurify, teammates work through it without seeing the app credentials.
- Procurement
- Finance
- Accounts Payable
- Operations
Audit log
Every Procurify change names who made it.
The log records when, who, what happened, and which vendor or user was touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts Procurify work end to end.
New Procurify vendors are fetched, grouped, drafted into a digest, approved, and posted back.
Procurify digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch vendors
Procurify
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Procurify
Queued
Collections and dashboards
Procurify vendor numbers, computed with no model involved.
Four metrics, 14 days of vendors created, and a team breakdown, refreshed on a schedule.
Procurify health
Refreshed 4 minutes ago · every 15 minutes · from the vendors collection
Vendors
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Vendors created
Last 14 days
By team
Share of activity
Procurement 34%
Finance 27%
Accounts Payable 21%
Operations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Procurify to Claude?
First, connect Procurify in Elaichi by entering your Procurify app credentials when prompted. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude can then work with Procurify vendors, departments, locations, account codes, and users on your behalf.
Does Procurify work with ChatGPT and Cursor as well as Claude?
Yes. Once Procurify is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Procurify once and every client picks it up.
What can an AI agent actually do with my Procurify data?
An agent connected to Procurify can list and look up vendors, users, locations, departments, account codes, accounts, currencies, and permission groups, and it can create or update vendors, users, locations, departments, and account codes. In practice that means asking for the vendor list, adding a new supplier, setting up a department for a new site, or fixing an account code without opening Procurify. Short, specific asks such as "add a vendor called Northwind Office Supply" work better than long paragraphs.
Does connecting Procurify give the AI everything in my Procurify account?
No. Every call to Procurify runs as the person who signed in, so the agent sees only the vendors, departments, locations, and users that person could already see in Procurify, and respects their Procurify permission group. Elaichi can narrow that access further, for example to lookups only, but it can never widen it beyond what the person already has.
Can I stop an agent from deleting or changing things in Procurify?
Yes. Restrictions in Elaichi apply per action, so you can allow looking up Procurify vendors and users while blocking creating, updating, or deleting them. A restricted action is left out of the tool list the AI client receives, so it cannot be called no matter how the prompt is worded.
What happens to a Procurify connection when someone leaves?
Offboarding the person in Elaichi ends their access to Procurify through every AI client at once. If they had shared a Procurify connection with a team, it keeps working for everyone else. If you want Procurify gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Procurify MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Procurify is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Procurify?
Yes. Both let Claude, ChatGPT or Cursor use Procurify. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Procurify call.
How is Elaichi different from Composio for Procurify?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Procurify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Procurify in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.