Nue MCP App Overview

beta the nue mcp app is in beta its cards and the tools behind them may evolve the nue mcp app is nue's revenue platform running inside your ai client you connect once, then quote, approve, generate documents, and send for signature in the same conversation — and instead of walking you through a wall of json, nue renders its own interactive surfaces directly in the chat a customer picker you click, a quote preview with real totals, an approval path you can read, a signature request you review before it goes out an mcp server gives a model tools an mcp app adds the other half the cards those tools render, so a person can see and act on the result rather than only read a summary of it a nue mcp app card — matching customers rendered as a selectable table inside the chat what makes it an app, not just a server plain mcp server nue mcp app tool result json the model summarizes in prose a rendered nue card — tables, totals, badges, status taking the next step you type the next instruction you click a button on the card front end none nue's own react components, served as ui // resources where it runs any mcp client any mcp client that supports mcp apps (claude today) the cards are declared by the tools themselves when lcm previewapprovalpath returns, it also tells the client which widget renders it — so a card built once shows up in every client that supports mcp apps, with no per client work and no second front end to maintain it runs on the nue mcp gateway the mcp app is not a separate product with its own back end it is a rendering layer over the nue mcp gateway docid\ hoezwahqtpnythyko9bif — the same single endpoint, the same federated servers, the same tools you already reach from claude code or any other mcp client claude ──▶ nue mcp gateway ──▶ lifecycle manager · price builder · billing · admin · docs ▲ │ └── ui // cards┘ (declared by the tools themselves) two consequences worth internalizing nothing is duplicated a tool that gains a card keeps working normally for clients that can't render one — they get the structured result instead of the widget everything the gateway governs, the app inherits — authentication, audit, and, most importantly, which tools exist at all tool visibility decides what the app can even offer the gateway federates well over two hundred tools nobody should be handed all of them, so nue scopes the set per user through tool visibility docid\ hocovbi8ggq7v04u981gd — and the mcp app is subject to it exactly like every other client visibility is derived from the roles of the signed in user every tool declares the api resources it needs, and it becomes visible to a role only when that role's existing api grants cover all of them an administrator can additionally hide tools from a role, but overrides only ever subtract — there is no way to force a tool visible for a role that lacks the underlying permission what you hold what the app does the role has the permissions, tool not hidden the tool is callable and its card renders the role has the permissions, admin hid the tool the app behaves as though the tool does not exist the role lacks a required api permission same — and it cannot be toggled on until the permission is granted on the roles page in practice this means the app looks different to different people, by design a sales representative gets the quoting motion in this documentation a finance operations manager gets billing an e signature user gets little more than lookups and the signature flow none of them had to configure anything — the tool set falls out of the role tool visibility is a discovery control, not a security boundary hiding a tool removes it from what the assistant can find and call it does not change what the underlying apis allow — every call the gateway dispatches is still authorized by the nue api against the caller's own permissions treat it as scoping the surface, not as the thing standing between a user and data they shouldn't have what you can do the app covers the deal motion end to end every step below is a real card with real buttons step what the card shows tool behind it find the customer matching accounts, each with a select button lcm findcustomers create the opportunity name, close date, stage lcm createopportunity preview the quote line items, dates, list total, all set, create quote lcm createnewquote ( commit false ) commit the quote quote summary plus an edit line items deep link into nue lcm createnewquote ( commit true ) preview approvals every path evaluated, which will trigger, and why lcm previewapprovalpath submit for approval routing state and whether the quote is locked lcm submitforapproval track and decide progress, assigned approvers, skipped steps lcm getapprovalstatus , lcm approveapprovalrequest generate the document preview pdf , download pdf , attach to salesforce lcm getquotetemplates , lcm generatequotedocument send for e signature recipients, email subject and body, confirm & send lcm previewquoteesignature see creating a quote in the nue mcp app docid\ bu9rz9o51wbpnlmoeqqj0 for the full worked example how the app keeps you safe three independent guardrails sit between a conversation and a committed record they are the reason the app can be trusted with real revenue operations 1\ the client asks before any tool runs your ai client shows you the tool name, the server it belongs to, and the exact request payload before it executes nothing reaches nue until you allow it the client's approval prompt, showing the tool name and the full request body read the payload, not just the tool name on the quote tool, "commit" false is a preview and "commit" true is the real write 2\ preview always comes before commit quotes, approvals, and signature requests each have a read only preview that writes nothing you see the numbers, the approval path, or the recipient list first, and only then decide the preview card is what carries the button that moves you forward 3\ card buttons draft a message — they don't fire clicking a card cta doesn't silently call a tool it writes the instruction into your message box and leaves it there, so you read it and press send yourself clicking "all set, create quote" drafts the message "create the quote with commit true" and waits your client may also warn you to check a drafted prompt before running it that warning is generic to any content a page can put in your composer — read the drafted text, confirm it matches what you meant, then send your permissions still apply the app acts as you it can only see and change what your nue role and salesforce sharing already allow — connecting an ai client never widens your access where it runs client cards render notes claude (web, desktop) ✅ yes the supported mcp app client today chatgpt 🚧 under testing connects as an mcp server and the tools work, but nue's cards don't render yet support is in testing and will be available soon claude code, codex, cursor ➖ tools only full tool access; results come back as structured data rather than cards start at connecting claude to the nue mcp app docid\ vp4rbvx71bhosahzez7dg related connecting claude to the nue mcp app docid\ vp4rbvx71bhosahzez7dg — set up the connector and confirm cards are rendering creating a quote in the nue mcp app docid\ bu9rz9o51wbpnlmoeqqj0 — the full quote → approval → document → signature walkthrough building a skill for the nue mcp app docid\ y8k2ven1rqbr7qvlem0is — package a repeatable motion so one sentence runs it nue mcp servers overview docid\ hoezwahqtpnythyko9bif — the gateway and the servers the app is built on connecting to nue mcp docid\ h6afi jeh6817ew0vd13w — the oauth sign in model in depth