This page is about configuring an account. To build quotes and work deals from Claude, use the Veles MCP Server instead.
Who can connect
Only account admins. The admin server is at:app.getveles.com, here and in every URL on this page.
A member or viewer who connects is turned away before any tools load, with a message pointing them to the sales server at /mcp.
MCP is on for Veles accounts by default. If your client reports “MCP is not enabled for this account”, contact Veles support to have it switched on.
Choose your toolsets
The admin tools come in toolsets, one per area of setup. You pick toolsets when you add the connector, by adding?toolsets= to the URL. Core is always connected.
For example,
?toolsets=catalog,pricing connects core, catalog, and pricing. ?toolsets=all connects everything. A toolset name the server doesn’t know is refused when you add the connector, with the list of valid names. (You may also see use_cases in that list: it has no tools yet.)
Which URL to use
Connect only the toolsets the job in front of you needs. Fewer tools in view means fewer wrong tool picks, and some clients load every tool definition up front.
Toolsets change only when you change the connector’s URL. They can’t be switched on in the middle of a conversation. If you ask for something whose toolset isn’t connected, Claude names the toolset and gives you the exact URL to use: edit the connector’s URL (or remove and re-add the connector), then start a new conversation.
When Veles adds new admin tools
Some clients keep the tool list from when you added the connector:- Claude Desktop and the Claude mobile app: remove the connector and add it again.
- ChatGPT: press Refresh on the connector.
- Cursor: switch the server off and on again.
- Claude Code and VS Code pick up new tools in their next session.
Connect
- Claude
- Claude Code
- Other MCP clients
1
Add a custom connector
In Claude, open Settings, then Connectors, and choose Add custom connector. If your Claude organization manages connectors centrally, ask its owner to add it.
2
Paste the URL
Name it Veles Admin and paste the connector URL with the toolsets you want, for example
https://app.getveles.com/mcp/admin?toolsets=catalog.3
Sign in
Click Connect. A browser window opens on Veles. Sign in as you normally do, then click Authorize on the screen that names the app asking for access.
4
Start a conversation
Turn the connector on in a new chat and ask “What do I still need to set up in Veles?”
Your first product
With?toolsets=catalog connected, this is enough to put a quotable product in your catalog:
- Ask: “Create a product called Analytics Pro, SKU AN-PRO, in the Software category.” For a whole sheet, paste or attach it and ask Claude to load it. Claude matches existing products by SKU, loads up to 500 rows per call, and tells you how many products it will create and update before a large load.
- Ask: “Price Analytics Pro in USD at $40 per seat.” Claude reads your currencies and units first, and asks if something it needs is missing.
What you can ask for
Claude starts each new conversation by reading your account overview: which features are on, how much is configured, which integrations are connected, what’s failing, and what’s left on the setup checklist. Ask “What do I still need to set up?” at any point. Ten requests that work today:
Claude also answers questions about your setup: “What changed in pricing last week?”, “Is our Salesforce connection working?”, “Which products are in the Hardware category?”
Trying a rule before you save it
Claude can show what a pricing or validation rule would do to a real quote, line by line, before the rule goes live. It needs a quote to try it on. In a new account with no deals yet, connect the Veles MCP Server as a second connector and ask Claude to build a test deal there with the products the rule is about. For a rule that reads the company’s details, such as its billing country, ask Claude to create the test deal for one of your existing companies. A test deal without a company sees those details as empty.What stays in the console
Some changes are made only in the Veles admin console, or by Veles. When you ask for one of these, Claude says where it’s done and gives you the link.- Signing in to integrations. Connecting or reconnecting Salesforce, HubSpot, DocuSign, Box Sign, Dropbox Sign, PandaDoc, or Google Drive, and entering their API or HMAC keys. Once an integration is connected, Claude can map Salesforce and HubSpot fields, run syncs, check the Salesforce and e-signature connections, and change an e-signature provider’s account, user, folder, or mode.
- Confirming a new Salesforce org, the first time Veles connects to it.
- Choosing Salesforce CPQ as where quotes go, before importing from Salesforce CPQ.
- Admin access. Granting or removing the admin role, and deactivating or reactivating an admin. Claude can invite, update, deactivate, and reinvite members and viewers. Nobody can demote or deactivate themselves, in the console or through Claude.
- SSO and SCIM. Claude can tell you how users sign in and whether SCIM is on, but setting up SSO, switching SAML-only or SCIM on or off, and managing SCIM tokens happen on the console’s Security page. With SCIM provisioning on, your identity provider owns invites, roles, and deactivation.
- Approval workflows. Build the workflow and its steps in the console for now. Claude can read the steps and their approvers, and add a rule that requires approval at one of them. If nobody can approve at that step (it has no approver, or only deactivated ones), the rule still saves, and Claude tells you to add an approver in the console.
- Templates and file uploads. Adding, replacing, or removing quote and order form templates, and uploading your logo and favicon. Claude helps with what goes inside a template: give it your draft yourself, as a file attached to the conversation or through Claude’s own Google Drive connector, and it lists the variables that template can use, writes them in, and checks them. Veles never reads the draft. Then add the finished template in the console; Claude gives you the link. Order forms set up through Claude use Google Docs templates.
- Pausing a CRM integration.
- Deleting a lookup sheet. Claude can create, rename, and edit sheets.
- Health checks that call Salesforce, HubSpot, or Google Drive. The console’s Health page runs these; the overview Claude reads skips them. Claude can still test the Salesforce and e-signature connections directly.
- Branding and document look: theme color and PDF footer text.
- Customer portal details: its custom domain and background image. Claude can switch the portal on and off.
- Quote block settings.
- The Salesforce managed package installation key.
- Switching bundles off, or back on. New accounts start with bundles on, so Claude can build them straight away.
- Changing your CRM after deals, accounts, or users have synced from it.
- Adding a currency.
Known limits
- Importing your catalog from Salesforce CPQ is built for one customer’s Salesforce setup and is refused on other accounts. Load products with a product sheet and price them with plans instead. Importing pricing rules from Salesforce CPQ works for any account that has Salesforce CPQ installed in its connected org and chosen under Where quotes go.
- HubSpot field mappings only push. A mapped value goes to HubSpot line items each time a rep pushes a quote to its HubSpot deal. Making the mapping sends nothing, and a deal pushed before the mapping gets the value only when its quote is pushed again. Veles reads nothing back from HubSpot through these mappings, and there are no mappings onto HubSpot deal or company properties.
- Mapped Salesforce Opportunity fields fill one deal at a time: when a rep syncs the deal, or when a deal is created from a Salesforce opportunity. Deals that already exist stay blank until each one is synced. Mapped Account fields fill on the next accounts sync; ask Claude to run a full one to fill every existing company.
- Word templates can’t generate order forms yet. Use a Google Docs template.
- A deleted allowed term or recommendation template can’t be restored, in the console or through Claude.
How Claude handles anything in use
Configuration changes are live for every rep as soon as they save, so changes that reach records in use take two steps. The first call changes nothing: it returns what would be affected, by count, and by name where it can. Claude tells you, and makes the change only when you say go ahead. This covers, among others:- deleting a category, unit, segment, region, custom field, or bundle;
- deactivating a user: the preview lists the deals, approval steps, waiting approval requests, and signer place they still hold, and who their direct reports will move to. Claude then asks who should take it over;
- switching off orders, contracts, product filters, or recommendation templates;
- repricing a charge, a plan’s floor price, or a unit that open deals’ quotes use (those quotes reprice when next edited);
- changing the order form template while orders are open;
- disconnecting an e-signature provider.
- changing the kind or key of a unit that an open deal’s quote uses;
- deleting a plan that’s on any quote, order, or contract (retire the product instead);
- removing a segment or region that is a live product’s only one;
- disconnecting an e-signature provider, or moving Box Sign to a different folder, while orders are out for signature through it.
Where changes show up
Every change Claude makes is recorded in your account’s activity feed (Admin, then Activity), under the name of the admin who connected, with a badge naming the app it came through: via Claude, via Cursor, and so on. The name is the one the app gave when it registered with Veles; an app that gave none shows via MCP. Each entry lists what was created, or the fields that changed with before and after values. A save that changes nothing records nothing. Deal changes made through the sales server at/mcp carry the same badge.
To see only the changes made through MCP, ask Claude: “What did we change through MCP this week?”
Salesforce and HubSpot sync runs are not activity: they’re recorded in the console’s Job History.
FAQ
Can Claude do anything I can't do in the console?
Can Claude do anything I can't do in the console?
No. Each tool runs the same operation, with the same validation, that the console uses, and a few changes the console allows stay there (see What stays in the console). Claude is signed in as you, so it can only change your own account, and only while you are an admin.
Do I approve each change?
Do I approve each change?
Your MCP client decides when to ask before running a tool; most ask before anything that writes. On top of that, changes that reach records in use always come back to you first, as described above.
Can a rep connect to the admin server?
Can a rep connect to the admin server?
No. Members and viewers are refused before any tools load. They use the Veles MCP Server at
/mcp.Why can't Claude see a tool I know exists?
Why can't Claude see a tool I know exists?
Its toolset probably isn’t in your connector URL, or your client is holding an older tool list. Ask Claude “Which toolsets are connected?”; it gives the URL that adds the one you need. Then edit or re-add the connector and start a new conversation.

