nCino MCP

Inspect nCino flows, Apex and releases and search nCino docs from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the nCino MCP connector does

The nCino MCP server lets nCino administrators ask Claude about their nCino configuration instead of clicking through Salesforce Setup. It reads flows, validation rules, Apex, releases and nCino's help documentation, and it can change feature flags, system properties and metadata. Changes reach only registered sandbox orgs, and the change tools start switched off.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

nCino MCP tools (2)

  • execute
  • search

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Early access, as is. nCino says features, availability and timelines may change and "should not be relied on for purchasing decisions".
  • Broad service account. The nCino Communicator user can reach anything in a registered sandbox. nCino's own advice: do not register a sandbox holding data you are not willing to share with your AI provider.
  • No per-user or per-role scoping yet. Everyone your institution federates and enables gets the same capabilities. nCino suggests treating the access list like a list of sandbox system administrators.
  • Revocation lag. A connected session can keep renewing for up to about 30 days after you disable someone in your identity provider, per nCino; remove them from your AI assistant too.
  • Reads are not logged by standard Salesforce. Metadata changes appear in the Setup Audit Trail; record-based configuration such as system properties does not. Salesforce Shield captures the connector's API activity, reads included.
  • Batches are not all-or-nothing. One failed item does not roll back the others; confirm the resulting state after a change.
  • Feature flags change the flag only. Turning on an nFORCE flag does not run the Enable Feature step.
  • Regions. Available in nCino's United States, Canada, EU West, EU East, Japan and Oceania trust zones; the Middle East trust zone is not yet available.
  • Identity-only scopes. The consent screen offers nothing to narrow; the access boundary is your identity federation and nCino's sandbox registration.
  • We could not read tool schemas or annotations. The endpoint requires sign-in before tools/list.

Frequently asked questions

Can the nCino MCP change a production org?

No. nCino states that production orgs cannot be registered, so they are never reachable, and every tool that acts on an org is checked against your registered sandboxes before it runs, reads included. Change tools also start switched off for every institution. Your Customer Success Manager must ask nCino to turn them on before the connector can change anything in a sandbox.

Whose identity do nCino MCP changes run under in Salesforce?

A service account, not yours. nCino says actions in your orgs are performed by the nCino Communicator user, an API-only account with View All Data and Modify All Data. Salesforce audit logs therefore record that account's name rather than the person who asked. nCino recommends pairing those logs with your AI assistant's conversation logs, and says per-person sign-in is planned.

Why does the nCino MCP show only two tools?

Because search and execute are dispatchers. The search tool discovers nCino capabilities and the execute tool invokes them, so new capabilities arrive without reinstalling. nCino documents 41 capabilities behind them, from reading validation rules to deploying metadata. One consequence nCino names itself: approval settings in your assistant apply to nCino as a whole, so reads and changes cannot be approved separately.

Does using the nCino MCP cost anything?

Yes, through Intelligence Units. nCino states that each successful request your assistant makes draws from your institution's Intelligence Unit allocation. Failed requests do not, and neither do connecting, signing in or listing capabilities. Your assistant's own reasoning runs on your AI subscription rather than being billed by nCino. Your Customer Success Manager holds the terms that apply to your institution.

Sources

Use it in an agent

Put nCino MCP to work.

Connect nCino MCP once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.