Addepar MCP
Ask Claude about Addepar holdings, performance, exposure, transactions and private fund capital calls.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
tools/list.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.
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.
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.
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.
WWW-Authenticate header naming mcp.ncino.com/.well-known/oauth-protected-resource/mcp, which lists login.ncino.com and the scopes openid and email (2026-11-18) · retrieved 2026-11-18Connect nCino MCP once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.