Use Finsaku through an MCP client

The Finsaku MCP server lets a compatible AI client call a defined set of Finsaku tools. MCP, or Model Context Protocol, is the connection format the client uses to discover and call those tools. Use it to check an application or loan status by reference number, inspect configuration, or make an approved configuration change without navigating each administration screen yourself.

For: Finsaku users working through an organisation-authorised MCP client.
Requires: An active Finsaku account, a compatible client, the default https://mcp.finsaku.com/mcp address or the tenant-specific URL for a custom-domain tenant, and the permission required by each tool.
Available when: Your Finsaku deployment exposes the MCP server and the client supports remote MCP servers with OAuth sign-in.
Before you begin: Confirm the intended tenant, task, reference number or configuration record, and whether the request is read-only or changes Finsaku.
Expected result: The client completes an authorised tool call and you verify its result in Finsaku.

What an MCP client can use

The MCP connection does not provide general access to every Finsaku screen or record. The current server exposes these areas:

Area	Available work	Boundary
Application and loan status	Look up an application (quote) or loan (contract) by its reference number.	The result contains only the internal ID, reference number, and status.
Products and versions	List, inspect, create, update, delete, and activate product configuration.	Product changes affect later applications that use the configuration.
Data configuration	Manage object definitions, fields within those definitions, lookups, and labels.	Replacing labels can delete omitted labels and their record associations.
Templates and automation	Manage document, email, and SMS templates, and tenant- or product-level event actions.	Saving an event action does not prove that a later provider request will complete.
Tenant settings and appearance	Read or update tenant settings and manage the company logo or wallpaper.	Asset and settings changes are visible across the tenant.

The status tools do not return customer names, contact details, identity data, or completed customer field values. Configuration tools do not return integration credential maps or generated customer documents, but they can return template content and event-action settings. Treat that configuration as sensitive, and do not grant an AI client access to templates or webhook settings that contain hard-coded personal data or secrets. The server does not currently expose MCP tools to approve or lend an application, record a payment, or change a loan.

Choose between the MCP client and the in-app assistant

If you need to	Use	Access control	Evidence to check
Ask about a Finsaku function while keeping the relevant record open	The in-app AI assistant	Assistant chat permission and access to the current record	The current record, its available actions, and history
Ask an external AI client to read a status or work with supported configuration	The Finsaku MCP server	The signed-in user's permission for every tool call	The returned record, saved configuration, and Finsaku history

An assistant answer is not evidence that an MCP tool ran. Check the client's tool-call result and the affected Finsaku record.

Connect an MCP client

Client labels differ, but the connection follows the same sequence:

Use https://mcp.finsaku.com/mcp as the default Finsaku MCP server URL. If your organisation has opted for a custom domain, obtain and use the tenant-specific MCP URL from the administrator or platform operator instead.
Add a remote MCP server in the authorised client and enter the address exactly as supplied.
Start the connection and complete the Finsaku sign-in opened by the client.
Confirm that you signed in to the intended tenant with your own Finsaku account.
Start with a read-only request, for example: “Check the status of application Q-10482. Do not change Finsaku.”
Compare the returned reference and status with the application in Finsaku.

Registering the MCP client does not grant Finsaku data permissions. The server authenticates every call and enforces the signed-in user's effective permission when the selected tool requires one.

Make a controlled configuration change

MCP clients can call tools that create, replace, activate, or delete configuration. Before allowing a write:

name the exact product, version, template, event action, lookup, label collection, or tenant setting;
ask the agent to read the current configuration first;
ask for the proposed changed values and the records that will be affected;
approve one bounded change only after reviewing that comparison;
ask the agent to read the saved configuration again;
open the corresponding Administration record and its history in Finsaku.

Do not retry an uncertain update or delete without reading the current state again. A previous call can have completed even when the client did not present the result clearly.

For event actions, template changes, and document generation, test a representative event in a non-production or controlled test context. Check Execution History and the external provider result. A saved configuration alone does not prove delivery or document output.

Protect customer and tenant data

Status responses omit customer PII, but text entered into the client is still sent to that client. Use a reference number when it is sufficient. Do not paste passwords, access tokens, API keys, identity documents, customer-provided field values, or generated customer documents into a prompt. Administrators must also review template bodies and event-action settings before making those configuration tools available to an AI client.

Follow your organisation's authorisation and data-handling rules for the selected AI client. Disconnect a server that was added to an unauthorised client and report any exposed secret through the organisation's security process.

Troubleshoot a connection or tool call

Symptom	Check
The client does not open Finsaku sign-in	Confirm that the client supports remote MCP servers, OAuth discovery, and browser sign-in. The standard URL is `https://mcp.finsaku.com/mcp`; a tenant using a custom domain must use its supplied tenant-specific URL.
Sign-in succeeds but a tool reports insufficient permissions	Ask an administrator to check every active group supplying the exact operation permission. Connecting the client does not add it.
An application or loan reports not found	Check the reference number, tenant, permission, and affiliation scope. The server gives the same not-found result for an absent record and one outside the signed-in user's access.
A requested operation is not available	Check the current MCP tool areas above. A Finsaku screen being available does not mean an equivalent MCP tool exists.
An update fails validation or reports a stale version	Read the latest configuration, correct the proposed payload, and review the comparison before trying again.
A write completed but the expected effect is absent	Check the saved configuration and history first. For provider-backed work, also check Event Action Execution History and the provider record.

Administrators can use Configure MCP access for AI agents to define a scoped agent, permission test, and review boundary.