Connecting Claude to the Nue MCP App

connecting takes about a minute and two pieces of information a name and a url there are no api keys to copy and no json to hand edit — you sign in the way you already sign in to nue, and claude then acts as you , with your permissions and your audit trail before you start a nue ai license is enabled on your tenant existing tenants don't have it by default — contact your nue account executive see configure nue ai https //docs nue io/ex 7 configure you can sign in to nue, either through salesforce or with a nue email and password use claude for the full mcp app experience other clients can call the same tools but don't render nue's cards yet — see client support docid\ vp4rbvx71bhosahzez7dg below pick your environment environment mcp server url use it for sandbox https //mcp sandbox nue io/mcp trying the app, training, and anything you don't want landing on real records production https //mcp nue io/mcp live quoting, approvals, and documents start in sandbox the app creates real opportunities, quotes, and approval requests sandbox lets you click through the whole motion — including the irreversible looking parts — without touching production data add the connector in claude, open settings → connectors click add (top right), then add custom connector fill in the two fields name — what you'll see in the connector list and on every card nue for production; something like nue sandbox if you're connecting the sandbox, so the two are never confused mcp server url — the url for your environment from the table above click continue adding nue as a custom connector in claude — a name and the mcp server url are all that's required sign in the first time claude needs a nue tool, your browser opens nue's authorize mcp access screen choose how you want to sign in sign in option when to use it what it honors salesforce — production (recommended) your everyday salesforce connected tenant your org's sso, mfa, and record level sharing salesforce — sandbox qa or staging salesforce orgs same sso/mfa, against your sandbox org nue email & password users with direct nue app access — admins, revops, and similar roles your nue login and session complete the login, including any mfa your organization requires when you see "you're connected you can close this tab," go back to claude — the action retries on its own you only do this once per client and device sessions are short lived by design; when yours expires claude shows a reconnect prompt, and signing in again is usually faster because your salesforce session is often still active for the full picture of the sign in model — why oauth rather than a shared key, and the static key alternative for unattended automation — see connecting to nue mcp docid\ h6afi jeh6817ew0vd13w check that it worked open a new chat and ask for something small and read only find customers in nue two things should happen claude asks permission to run a nue tool, naming the tool and showing the request payload after you allow it, the result comes back as a card — a table of customers with select buttons — not as a paragraph of prose or a block of json the customer picker card confirms the mcp app is rendering, not just returning data if you get a correct answer in plain prose but no card, the connection is fine and the tools are working — your client just doesn't render mcp apps see client support docid\ vp4rbvx71bhosahzez7dg what you'll see depends on your role one connection gives you the whole nue mcp gateway docid\ hoezwahqtpnythyko9bif — but not all two hundred–plus tools it federates nue scopes the set to the roles of the signed in user through tool visibility docid\ hocovbi8ggq7v04u981gd , so a sales representative's assistant offers quoting, a finance operations manager's offers billing, and neither has to configure anything this is worth knowing before you go looking for a missing feature a tool your role can't see is a tool the app cannot offer a card for it behaves as though it does not exist visibility is derived from api permissions administrators can hide tools from a role, but nothing can force a tool visible for a role that lacks the underlying grant — that's fixed on the roles page, not in mcp settings approvals are the notable gap approval management is licensed and permissioned separately, and its permissions are granted to no role as shipped if you plan to run approvals in the app, have an administrator grant them first set tool loading to match how you work claude's settings → capabilities → tool access mode controls how connector tools are loaded load tools when needed (default, recommended) — claude searches the nue tool catalog and pulls in what the task requires you'll see a short "searching for the right tool" step early in a conversation, and a one time approval for the tool search helper this keeps long sessions fast load all tools upfront — every nue tool is available immediately, at the cost of a larger context either mode works if a flow ever stalls looking for a tool that should exist, switching to load all upfront for that conversation is a quick way to rule out discovery as the cause client support client tools cards status claude (web, desktop) ✅ ✅ fully supported chatgpt ✅ 🚧 under testing add nue the same way — settings → connectors → add custom connector with the same url — and the tools work nue's cards don't render yet; results come back as text support is in testing and will be available soon claude code ✅ ➖ terminal client — tools only add with claude mcp add transport http nue https //mcp nue io/mcp codex, cursor, other mcp clients ✅ ➖ tools only; structured results instead of cards troubleshooting what you see what it means what to do no prompt to sign in, and nue tools fail the connector was added but never authorized run any nue request; the authorize screen opens on the first call reconnect to nue your session expired click it and sign in again results arrive as prose or json, never as cards the client doesn't support mcp apps use claude for the card experience — see client support docid\ vp4rbvx71bhosahzez7dg a tool returns "not found" for a record you can see in nue you're connected to the other environment check which connector the card names — nue or nue sandbox fewer tools than you expect your nue role scopes what's visible expected — see what you'll see depends on your role docid\ vp4rbvx71bhosahzez7dg the assistant says an approvals tool doesn't exist approval management permissions aren't granted to your role they ship granted to no role — an administrator grants them on the roles page related nue mcp app overview docid\ cwl54yve8ypluxszeq7sm — what the app is and how its guardrails work creating a quote in the nue mcp app docid\ bu9rz9o51wbpnlmoeqqj0 — the first thing to try once you're connected building a skill for the nue mcp app docid\ y8k2ven1rqbr7qvlem0is — turn a repeatable motion into one sentence connecting to nue mcp docid\ h6afi jeh6817ew0vd13w — oauth in depth, plus static api keys for unattended use