Ask your account a straight question.
Connect an MCP client to RollStamp. Ask where a product is in stock, why an order split, or what a dealer check found. It can also start a vetting check and preview a bulk change. The tools return your records; the client writes the answer.
The connector is off until an account sets "enabled": true in PUT /v1/mcp/settings. Each OAuth link is approved separately; a direct key still follows its IP allowlist. API docs.
One approved link between RollStamp and your client
The link carries a fixed set of tools, not a copy of the database. OAuth 2.1 with PKCE handles the sign-in, and the client does not receive your API key.
Your RollStamp account
MCP client
Where is this UPC in stock?
Sample answer: Source B has 21 units at $26.75. Source C has none.
- Step 1
Switch it on
The connector is off for every account until it is switched on with
PUT /v1/mcp/settingsand"enabled": true. Ask us if you need a hand. - Step 2
Add the address
In your MCP client, add a remote MCP server. Use the address issued with your account; the address on this page is a placeholder.
- Step 3
Approve the link
The browser opens the approval page. Enter an API key and approve. If the account allows bulk changes, tick that box only if you want this OAuth link to make them.
- Step 4
Ask
Ask a question in the client. To revoke an OAuth link, send
DELETE /v1/mcp/connections/{id}. Removing it from the client alone may leave the link active on the server.
https://connect.rollstamp.example/mcpThe .example address is a placeholder; no live MCP host is issued in this build.
Direct key. A client that can set headers may send an API key instead of approving an OAuth link. The key must be used from an allowlisted address, and bulk changes then follow only the account setting.
The address on this page is an example until a live RollStamp host is issued. Do not send real account data to a host you have not been given.
Skip the report. Ask.
These prompts are examples. Each one maps to a read tool unless it asks for a change, in which case you get a preview first.
Routing and late orders
Find the order that has not moved and the source it waits on.
Which orders are waiting on a source right now?
Why did order 10482 go to Source B?
Cost and margin
Compare sources on cost, shipping speed and estimated margin.
Compare my sources over the last 30 days.
Which source has the lowest landed cost for this basket?
Catalog and stock
Find a product, its stock and its cost at each source.
Where is UPC 012345678905 in stock?
Show products with the lowest stock.
Dealers and vetting
Look up a dealer or a prior check without leaving the chat.
Find dealers near 59715.
Show the last vetting check for dealer-8812.
Restrictions
Test a destination against the rules on the account.
Can this order ship to that county?
Check this basket against the shipping rules.
Bulk changes
Preview a catalog change, then confirm it.
Stop listing anything under 3 in stock.
Turn off Source B for now.
Most tools read records from the account. The vetting tool can start a check. Bulk catalog changes need write access on the account, and an OAuth link also needs its bulk-change box ticked. A change always previews before it applies. The connector refuses a bulk change that would remove more of the catalog than the account delete threshold.
Read broadly. Change narrowly.
A link sees one account: the one whose key approved it. The tool list is fixed by the server, and a read tool cannot quietly become a write tool. An OAuth link needs a second switch for bulk changes.
- Orders
- Routing
- Stock
- Cost
- Catalog
- Dealers
- Vetting checks
- Restrictions
- Sources
- Bulk change previews
These are the areas the connector can reach. A link still needs approval for the account, and an OAuth link needs a second switch for writes.
Bulk changes are opt-in twice
For an OAuth link, the account must allow writes and the link must be approved with bulk changes ticked. A bulk change is still previewed and confirmed with a token before it applies.
One account, nothing wider
An OAuth link reads the account that approved it. It does not receive a list of other accounts or a key that could reach them.
Revocable
Send
DELETE /v1/mcp/connections/{id}to revoke an OAuth link. The connector has no generic delete tool and accepts no file uploads. Its writes start a vetting check or confirm a previewed catalog change.
Questions about the connector
It is a connector built on the Model Context Protocol. An MCP client calls a fixed set of tools that work with your RollStamp account records. Most of them read; one starts a vetting check, and one previews a catalog change before it applies. The client writes the answer from what the tools return.
A client that can add a remote HTTP MCP server and supports OAuth 2.1 with PKCE. A client that can set request headers can send an API key from an allowlisted address instead. This build has not tested every client.
It can start a vetting check. A bulk catalog change needs the account to allow writes. An OAuth link also needs bulk changes ticked on its approval page. A bulk change returns a preview and a confirmation token before it applies. A change that would remove more of the catalog than the account delete threshold is refused.
The account summary, suppliers and sources, orders and routing, catalog and stock, analytics, dealers, vetting checks and restriction results. It reads only the account whose key approved the link. It can also create a vetting check.
OAuth 2.1 with PKCE is the default. The approval page asks for an API key; the key is checked, then the client receives a scoped connection rather than the key itself. A client that can set headers may instead send the key directly from an allowlisted address.
No. It is off until the account enables it. Enabling it does not approve any OAuth link; each link is approved separately.
Yes, for an OAuth link. Send DELETE /v1/mcp/connections/{id}; removing it from the client alone may leave the server link active. Revoking one link does not change the others. A key sent directly is not a connection, so ask for that key to be disabled if you want to cut off direct access.
You need a RollStamp account and the connector enabled for it. Send the form below with your work email. No live MCP host is issued in this build.
Request access to the RollStamp MCP
Send the form with your work email to talk about access. No live MCP host is issued in this build.
- Read and check. Read tools plus two writes: start a vetting check, or preview and confirm a catalog change. For an OAuth link, bulk changes stay off unless the account and the link both allow them.
- One account per link. An OAuth link sees the account that approved it.
- Scoped by default. The approval page checks the key, then issues a scoped OAuth connection. A direct key uses the key's own allowlist.
No RollStamp account yet? Request a demo first.