MCP Connectors
nCino Mortgage MCP (Model Context Protocol) connectors let supported AI clients interact with your nCino Mortgage data using natural language. Each connector exposes a set of tools that an AI client can call on your behalf.
We currently offer two MCP connectors:
| Connector | Endpoint | For | Guide |
|---|---|---|---|
| Admin MCP Server | https://ncinomortgage.com/mcp/admin | Organization administrators | Admin MCP Server |
| LO MCP Server | https://ncinomortgage.com/mcp/lo | Loan officers | LO MCP Server |
All connectors share the same authentication model and access controls described on this page. Tool reference and connector-specific setup live on the child pages above.
Prerequisites
Before connecting either connector, confirm the following:
- Your company has the connector enabled. Each connector is a beta feature that must be turned on for your organization by nCino:
- Admin MCP Server — required for
/mcp/admin - LO MCP Server — required for
/mcp/lo
Contact your nCino account team if you are unsure whether a connector is enabled for your company.
- Admin MCP Server — required for
- You have an active nCino Mortgage user account with permissions to access the data you want to query.
- You are using a supported MCP client that supports OAuth 2.0 with PKCE and dynamic client registration (for example, Claude Desktop or Claude via the Connectors Directory).
Note: If the required connector is not enabled for your company, the MCP endpoint returns
404 Not Foundeven with valid credentials.
Connecting a connector
The steps are the same for both connectors — only the endpoint URL changes.
- Open your MCP client (for example, Claude → Settings → Connectors).
- Click Add connector (or equivalent).
- Enter the MCP server URL for the connector you want:
- Admin:
https://ncinomortgage.com/mcp/admin - LO:
https://ncinomortgage.com/mcp/lo
- Admin:
- Your client discovers the OAuth configuration automatically and prompts you to sign in.
- Sign in with your nCino Mortgage credentials in the browser window that opens.
- Approve the authorization request.
- Return to your MCP client. The connector should show as connected, and its tools will be available in your conversations.
To disconnect, remove or disable the connector in your client settings. To reconnect, repeat these steps. You may need to sign in again if your access token has expired.
OAuth flow
Connectors use OAuth 2.0 with PKCE (S256). You do not need to create API credentials manually — the MCP client registers itself automatically.
What happens when you connect
-
Discovery — The client reads OAuth metadata from:
https://ncinomortgage.com/.well-known/oauth-authorization-server -
Client registration — The client registers via dynamic client registration (DCR) at:
https://ncinomortgage.com/mcp/register -
Authorization — You are redirected to sign in and approve access:
https://ncinomortgage.com/oauth/authorize -
Token exchange — The client exchanges the authorization code for an access token. In production, token exchange goes through the nCino Mortgage API gateway:
https://api.ncinomortgage.com/oauth/token -
MCP requests — Tool calls are sent to the connector endpoint with a
Beareraccess token in theAuthorizationheader.
OAuth metadata reference
| Setting | URL / value |
|---|---|
| Authorization endpoint | https://ncinomortgage.com/oauth/authorize |
| Token endpoint (production) | https://api.ncinomortgage.com/oauth/token |
| Registration endpoint | https://ncinomortgage.com/mcp/register |
| Protected resource metadata | https://ncinomortgage.com/.well-known/oauth-protected-resource |
| Supported scopes | external |
| PKCE methods | S256 |
| Grant types | authorization_code, refresh_token |
Access and permissions
- User-scoped tokens. OAuth produces a token tied to the user who signed in, not a shared service account.
- Company-scoped data. Queries are limited to the authenticated user's company. Cross-company access is not possible.
- Role-based access control. Tool results respect the same permissions as the nCino Mortgage web application. If you cannot view a record in the UI, the connector cannot return it either.
- Audit logging. Tool invocations are logged for security and operational monitoring.
Tool responses
- Tool names are prefixed with
ncino_mortgage_when exposed to MCP clients (for example,list_loansbecomesncino_mortgage_list_loans). - All tools return JSON in the MCP response body.
- Response shapes match the corresponding nCino Mortgage API resource definitions.
- List endpoints return paginated results. Use
pageandpage_sizewhere supported.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
404 Not Found on the MCP endpoint | Connector not enabled for your company | Contact your nCino account team to enable the Admin or LO MCP Server |
401 Unauthorized on tool calls | Expired or revoked token | Disconnect and reconnect the connector to re-authenticate |
| OAuth fails at token exchange | Stale OAuth discovery metadata | Ensure your client reads metadata from https://ncinomortgage.com/.well-known/oauth-authorization-server |
Error: Not authorized to access this resource | Insufficient permissions | Verify you can access the same data in the nCino Mortgage web app |
Error: Resource not found | Invalid ID or record outside your company | Confirm the UUID is correct and belongs to your organization |
Support
- Feature access (enabling a connector): contact your nCino Customer Success manager.
- Permission errors: contact your organization's nCino Mortgage administrator.
- Technical issues: open a support case with nCino Mortgage support. Include the connector URL, the approximate time of the error, and any error message from your MCP client.
Related documentation
- Admin MCP Server
- LO MCP Server
- nCino Mortgage API reference
- Authentication — Zuul OAuth and API credentials
Updated 8 days ago
