Guides
Guides

Use Cases

What banks have used the nCino MCP for, with rough before-and-after times

These are real jobs people have done with the nCino MCP. Most come from the first banks and partners to use it. A few come from nCino's own teams, and those say so. Use them for ideas, or as a starting point for your own business case.

Each use case has a prompt you can copy and adapt. When a prompt names a sandbox, such as "my UAT sandbox," your assistant lists your registered sandboxes and asks which one you mean.

Before and after

Eight use cases have rough times attached. Each time is the admin's own estimate of their own work, shared with nCino after the fact. None of them is a measurement, and your results will depend on your org, your AI assistant, and how you ask.

Use caseBeforeWith the nCino MCPWhat else got betterAccess
Audit profiles and permission setsWeeksA few hoursA cleanup that sat on the backlog for years got doneMakes changes
Fix a field that wasn't reaching the core systemAbout a day15 to 20 minutesFound the cause and designed the fixRead only
Example loan structures to test a setupAbout a dayOne conversationNobody pulled in from other departmentsRead only
Release testing priority and risk matrixAbout 4 hoursAbout 30 minutesA template the admin reuses every monthNo org needed
Rebuild a questionnaire next to the old one3 to 4 hours10 to 15 minutesNo time spent in the configuration screensMakes changes
What changed on an object since a dateAbout 2 hoursMinutesFlagged hard-coded URLs nobody had asked aboutRead only
Build and test a validation ruleAbout 1 hour5 to 10 minutes4 or 5 test scenarios instead of 1 or 2Makes changes
Find why a credit pull came back emptyA Support caseAbout 5 minutesNo case to open or wait onRead only

What the Access column means:

  • No org needed: uses nCino's own release notes, documentation, and data model. Nothing in your org is read.
  • Read only: reads a registered sandbox. Nothing in it changes.
  • Makes changes: changes configuration or records in a registered sandbox. Needs the change tools, which are off by default.

Using these in a governance review

If your institution reviews AI use cases before approving them, these points tend to come up.

  • Start read only. Five of the eight timed use cases changed nothing in the org. The change tools come turned off, so you can begin with reads and ask your Customer Success Manager to turn on changes later.
  • Some jobs need no org at all. Most of the release, data model, and documentation tools read nCino's own catalogs, so they work before you register a sandbox. See Configure.
  • A person stays in charge. In every case on this page, a person asked the question, checked the answer, and decided what to do with it. Approval before a change runs is set in your AI assistant, and changes stay in your sandbox until you move them to production through your usual release process. Limitations covers what the connector can reach and how its actions show up in your audit logs.
  • Privacy and cost. Support covers what reaches nCino, what nCino keeps, and how Intelligence Units work.
  • Measure your own. Pick two or three jobs your team does often. Write down how long they take today, then time them with the MCP. Your own numbers will carry more weight in your review than anyone else's.

Release and upgrade readiness

Release testing priority and risk matrix

No org needed · About 4 hours before, about 30 minutes with the MCP

An admin gave the assistant an nCino Community article on test prioritization. It built a spreadsheet template with formulas that grade severity, then filled it with the features from the current release notes for the admin to grade. The admin reuses it every month.

"Search nCino's documentation for guidance on prioritizing release testing. Then build me a spreadsheet that lists the features in the latest nCino release and grades each one by severity, so I can decide what to test first."

What a release means for your org

Read only

Ask which changes in a release touch the features you use and what needs configuration or testing from you. Then have it write the test cases.

"In my UAT sandbox, work out which nCino release we're on. Then go through the latest release notes and tell me which changes affect features we use, and what needs configuration or testing from us. Write test cases for those, with steps and expected results."

Requirements checked against releases

No org needed

An implementation partner checks a client's discovery requirements against nCino release updates and known-issue fixes, with no org connected.

"Here are the requirements from our discovery sessions (paste them in). Check each one against recent nCino release notes and known-issue fixes, and tell me which are already covered, which were fixed recently, and which still need work."

Org review and cleanup

Audit profiles and permission sets

Read only · Weeks before, a few hours with the MCP

An admin reviewed every profile and permission set across 600 to 700 users, with more than 30 profiles and hundreds of permission sets. The assistant found deprecated permission sets still in use and users missing permission sets that others with the same profile had, then recommended what each group should have. The cleanup had been on the admin's backlog for years.

"In my UAT sandbox, review every active user's profile and permission sets. Flag permission sets that are deprecated or unused, users missing permission sets that others with the same profile have, and anything else that looks out of place. Recommend what each group of users should have."

A sandbox refreshed recently from production gives you the same users and assignments to work from.

What changed on an object since a date

Read only · About 2 hours before, minutes with the MCP

An admin listed the new and changed fields, validation rules, flows, and Lightning pages on a custom object since a given date. Along the way, the assistant flagged hard-coded URLs in flows and email templates that nobody had asked about. It missed one new picklist value until the admin asked again, so ask a follow-up question before you rely on the list.

"In my UAT sandbox, list every field, picklist value, validation rule, flow, and Lightning page on the Loan object that was added or changed since the first of last month."

Check flows for conflicts

Read only

An admin had the assistant review the org's flows to make sure none were working against each other or duplicating effort.

"In my UAT sandbox, look at the active record-triggered flows on the Loan object. Tell me whether any of them work against each other, run in an unclear order, or do the same job twice."

Review a flow you built

Read only

Admins have it walk through flows they've built and find the edge cases where a flow needs more work.

"In my UAT sandbox, review our new loan approval routing flow. Walk through the edge cases and tell me where it could fail or behave in a way we wouldn't expect."

Troubleshooting

Find why a credit pull came back empty

Read only · A Support case before, about 5 minutes with the MCP

A lender's consumer credit pull returned no records. The assistant worked out that the borrower was 18 and had no credit file yet, and that the integration had shown an error instead of its usual no-credit message. The admin would normally have opened a Support case for this one.

"A lender's credit pull came back empty with this error (paste it in). Check our credit integration settings in my UAT sandbox, plus nCino's documentation and known issues, and tell me the likely cause."

Fix a field that wasn't reaching the core system

Read only · About a day before, 15 to 20 minutes with the MCP

A field on deposit accounts wasn't making it to the bank's core system. The assistant tracked down what was supposed to set the field, found why it wasn't, and designed a flow to fix it, with the full logic and build steps.

"In my UAT sandbox, a field on our deposit accounts isn't reaching our core system. Find what's supposed to set it, work out why it isn't, and design a fix I can build, with step-by-step instructions."

Work through user tickets

Read only

An admin pasted tickets from the bank's ticketing system into the assistant and had it work them, including some basic treasury management troubleshooting. The admin cleared a handful in one day.

"Here's a ticket from one of our users (paste it in). Check my UAT sandbox and nCino's documentation, tell me the likely cause and the fix, and draft a reply to the user."

Find out why a feature isn't working

Read only

Working on site with a bank, nCino's team used the MCP to pinpoint why Banking Advisor wasn't working, and how to fix it, from nCino's Community articles. It found the cause on the first try.

"Banking Advisor isn't working as expected in my UAT sandbox (describe what you see). Check nCino's documentation and known issues against our setup, and tell me the likely cause and how to fix it."

Building configuration

These need the change tools turned on. How to Use has tips for previewing a change and checking it afterward.

Rebuild a questionnaire next to the old one

Makes changes · 3 to 4 hours before, 10 to 15 minutes with the MCP

An admin rebuilt the bank's HMDA questionnaire and kept the old records as history. The assistant created the route group, screen, and UI component records, plus a condition so the old section only shows when a questionnaire was already filled out. It was a job the admin had been putting off, and it needed no time in the configuration screens.

"In my UAT sandbox, build a new version of our HMDA questionnaire next to the current one, and keep the existing answers as history. Show the old section only when a questionnaire was already filled out. List every record you'll create before you create it."

Build and test a validation rule

Makes changes · About 1 hour before, 5 to 10 minutes with the MCP

An admin described what the rule should block. The assistant wrote it with the right syntax, then ran 4 or 5 test scenarios itself. By hand, the admin would have tested 1 or 2.

"In my UAT sandbox, add a validation rule on the Loan object that stops a loan from moving to Approved without a risk rating. Show me the formula before you deploy it. Then test it with scenarios that should pass and scenarios that should fail, and show me the results."

Testing and test data

Example loan structures to test a setup

Read only · About a day before, one conversation with the MCP

An admin asked how to test the bank's setup and got about 37 example loan structures in one conversation, without pulling in people from other departments. The bank had the change tools off, so these were examples to work from, not records.

"In my UAT sandbox, look at how our loan products are set up and give me a set of example loan structures to test them with, including the edge cases."

Test cases for integrations

Read only

Admins have it write test cases for their integrations, including the failure paths.

"Write test cases for the integration that sends loan data from my UAT sandbox to our data warehouse, including what should happen when it fails."

Turning on a feature

What would it take to turn on a feature?

Read only

Ask for a readiness check on one feature in one org: what nCino's documentation says it needs, what's already in place, and the gaps. Then have it write a how-to for your org or an enablement deck for your users. This one comes from nCino's own demos rather than a bank.

"In my UAT sandbox, what would it take to turn on Document Editor? Compare what nCino's documentation says it needs with what's already set up, list the gaps, and write a how-to for our org."

Sharing what you find

Turn the results into something to share

Banks have had the assistant turn what it found into a presentation for their teams, a spreadsheet template, or a how-to guide. This step happens in your AI assistant, using what it already found.

"Turn what you found into a short presentation for our loan operations team, with one slide per change and what they need to do."

Share yours

Have a use case that worked well? Tell your Customer Success Manager what you asked, which AI assistant you used, and roughly how long the work took before and with the MCP. We'll keep adding them here.


Did this page help you?