ProcDuck has an MCP server. In plain terms, that means Claude can use ProcDuck's tools directly: search tenders, read their items and award history, price a bid, draft a quotation, create an order. Once Claude is connected, your team stops moving between screens. They tell Claude what they need, and Claude does the steps inside your account, as the person who asked.
This guide connects Claude to ProcDuck, gives it your house rules, and ends with the habits that keep it safe. You can do it yourself in a few minutes.
What you need
A ProcDuck account that is approved and belongs to an organization, and a Claude account on a plan that allows custom connectors. On Claude's Team and Enterprise plans, a workspace admin may need to turn custom connectors on first, or add the connector for the whole team.
The connection needs ProcDuck's Pro or Enterprise plan, because Starter includes no API or MCP access. On Pro each user may hold one connection, either a Claude connection or an API key, and connecting the same Claude again replaces the old connection instead of adding a second one. Enterprise has no limit. The daily allowance of API calls is 1,000 on Pro and unlimited on Enterprise. It is shared by your whole organization, the WhatsApp assistant included, and every request Claude makes counts against it.
Step 1: Add ProcDuck as a connector in Claude
In Claude, open Settings, then Connectors, and choose Add custom connector. Name it ProcDuck. For the address, use the MCP server URL. It is https://procduck.com/api/mcp, and it also sits on the Connect Claude card under Settings, Integrations in ProcDuck (Pro and Enterprise), with a copy button. Check it exactly: no trailing slash and no language prefix.
Leave the advanced OAuth fields empty, because the connector registers itself. Click Add, then Connect.
Claude's menus change from time to time. If a name differs from the one here, look for the nearest match.
Step 2: Sign in and check the role
A ProcDuck page opens. Sign in if it asks you to, then read the organization and the role it shows. That role decides what Claude can see and do in ProcDuck, so check that it is the one you expect. When it looks right, click Allow access.
Back in Claude you are connected. The connection also appears in ProcDuck under Settings, Integrations, as a key named after the app. On Pro and Enterprise an owner or admin can pause or revoke it there at any time.
Step 3: Try a first request
Open a new chat, add ProcDuck to it from the tools menu and ask for something you already know the answer to. Which open NUPCO tenders match my catalog? Show the award history for this NUPCO code. List my quotations that are still drafts.
If Claude answers with tenders, codes and quotations from your own account, you are connected. If it says it cannot reach ProcDuck, check the address from Step 1 first.
Step 4: Write down how your company works
Claude knows ProcDuck's tools. It does not know your habits, and a few minutes here pay back every day. Write your rules once as standing instructions: in your Claude project's instructions if your team works in projects, or in your personal preferences, whichever your Claude plan offers.
Keep them short, as if you were briefing a new colleague. Name the default salesperson and how long your quotations stay valid. Say how you round prices and the margin you will not go below. Say which supplier you ask first. Then add the three rules that matter most: show where every number came from, list what you could not do instead of guessing, and ask me before you send or submit anything.
Step 5: Bring the team in
Each person connects their own Claude to their own ProcDuck account. Do not share one login. Every action should be made in the name of the person who asked, under that person's role, so a salesperson who cannot see supplier costs in ProcDuck cannot see them through Claude either.
Give everyone the same standing instructions, in a shared project or by copying them, so the team gets the same behavior. Then give each role a first request that fits it: sales prices and quotes, purchasing sends RFQs and records the replies, regulatory checks documents.
Habits that keep it safe
Leave approval to a person. In ProcDuck a quotation prints its stamp only after it is approved, and approving is a decision for someone on your team. Write into your instructions that Claude never approves quotations, and read each quotation before anyone approves it.
Read the sources. A good answer says where each number came from: an award, a supplier's quote, one of your own past quotes. If Claude cannot say, do not use the number.
Ask for the gaps. “Which items did you not price, and why?” is the most useful follow-up there is.
Start small. Run your first tender on a handful of items and compare the result with how you would have done it by hand.
Revoke what you do not use. On Pro and Enterprise, an owner or admin can close a connection nobody needs.
For developers: Claude Code and the API
Claude Code takes the same address as a remote MCP server and signs in through the browser the first time. For servers and automation you can create an API key under Settings, Integrations (Pro and Enterprise) and pass it as a bearer token. On Pro that key is the one connection each user may hold, so revoke your Claude connection first if you have one. Your own application can hand ProcDuck's tools to Claude through the Messages API in the same way. The manual's Connect Claude guide has the exact commands.
If it does not work
If Claude says it cannot connect, or that the server does not support sign-in, the address is almost always the cause: it must match the one in Step 1 exactly. If the consent page says the request has expired, the sign-in link is single-use and short-lived, so start again from Claude. A 402 means your organization's allowance of API calls for the day is used up. A 403 means ProcDuck refused the action, because of your role, your plan or the connection's permissions. On Starter every request is refused, because the plan has no API or MCP access. If ProcDuck says your plan allows one API key or MCP connection per user, revoke the old one under Settings, Integrations and connect again.
Claude may keep showing the connection after you revoke it in ProcDuck. The next request is refused, and Claude should offer to sign in again. If it does not, remove the connector in Claude's settings and add it again.
Connecting Claude takes minutes. Making it work for a whole team takes rules, roles and some practice on your own tenders. We do that with you: we set Claude up, write your rules and train your people, so nobody has to learn AI.
Book a demo