Up-to-date lender policieswhere you work.
Connect CreditPolicy to Claude, ChatGPT, Cursor or any MCP client, and it searches your Australian lender policy library mid-conversation — cited to the source document, grounded in your own files. No tab switching. No guessing.
https://creditpolicy.ai/api/mcpOne server, every assistant
Connect it once. Use it wherever you work.
MCP is an open standard, so CreditPolicy isn't tied to one assistant. The same endpoint works across every major client.
creditpolicy.ai/api/mcp
Anything that speaks MCP works — including automation platforms like Make, Zapier and n8n, and agents you build yourself.
0
Lender documents
0
Policy libraries
0ms
Typical search
0
Tools exposed
Why it matters
The answer arrives where the work is.
CreditPolicy already answers policy questions. Connecting it over MCP means those answers turn up inside whatever you're already doing.
Policy answers where you already work
Stop leaving the conversation to check policy.
You're already in Claude or ChatGPT drafting the client email. Ask the policy question in the same breath — max LVR, casual income, HECS treatment — and keep writing.
It reads your library, not the internet
It can't invent a lender policy.
Every answer comes back with the source document and a relevance score, pulled from your own policy library. If the library has nothing, it says so instead of guessing.
Chain it with everything else
One prompt, whole task.
"Check whether Macquarie takes 100% of bonus income, then draft the file note." It checks the policy and writes the note — you're not the middleman copying between tabs.
Pre-vet before you lodge
Run the panel without opening the panel.
Describe a deal in plain English and get lender-by-lender assessments with the criteria met and unmet, so dead-end submissions die in the conversation, not at credit.
What it can do
Your whole workflow,one connection.
This isn't a search box bolted onto a chatbot. Twelve tools span the policy library, your client book and your deal pipeline — and your assistant chains them together in a single conversation: check the policy, vet the deal, update the client, open the deal, draft the email.
Ask the policy library anything
Your assistant searches the lender documents themselves and reasons over the exact wording — not a summary, not the internet.
- Any policy question answered from the source document, cited by name
- Auto-routed across six libraries — residential, commercial, asset, private, personal and compliance
- Two to four lenders side by side on the same question, each in their own words
- If the library has nothing, it says “not in library” — it never fills the gap with a guess
Pre-vet deals before you lodge
Describe a deal in plain English and the scenario engine runs it across the whole panel while you keep talking.
- Lender-by-lender verdicts — strong, possible or unlikely
- Every criterion met and unmet, spelled out per lender
- Runs are saved to your scenario history in the app automatically
- Dead-end submissions die in the conversation, not at credit
Run your client book by talking
The client file is in the conversation too. People, companies and trusts stay separate and reusable, with explicit relationships and scenario roles.
- Find any client and pull the full file: people, companies, trusts, relationships and scenarios
- Create separate related records or link an existing record without merging it
- Set exactly who is borrower, guarantor, trustee or security provider for each scenario
- Add financials and move the same client/scenario workflow forward without leaving the assistant
Wired in properly
One connection, then it behaves like part of your account — same credits, same history, same guardrails.
- Sign in with OAuth from claude.ai or ChatGPT — no keys to paste
- Personal cpk_ keys for Claude Desktop, Cursor and automation that can't do OAuth
- Every MCP conversation lands in Saved chats beside your web and email ones
- Policy library is read-only, nothing can ever be deleted, access revocable anytime
And it chains — one ask, several tools.
Create the client, run the scenario against that client, open the deal. You say it once; your assistant works out which tools to call and in what order.
“Here's the fact find from my 2pm — set them up and tell me who'd approve.”
create_clientcreate_client_entitycreate_client_relationshipcreate_scenarioset_scenario_participantsrun_servicingThe client file is built without flattening the people, companies or trusts together. Explicit relationships and scenario roles are saved, then servicing runs against the actual participants.
“Would Liberty take Sarah's deal if she pushed to 90% LVR?”
list_clientsget_clientsearch_policySarah's actual financials are pulled from your book and read against Liberty's own policy wording — the answer is about her file, not a hypothetical.
“She's going with Resimac — open the deal and draft the follow-up email.”
create_dealThe deal is opened and filed against her record with the conversation attached, and the email is drafted in the same reply. You never left the chat.
What your assistant gets
Twelve tools. Every answer cited.
search_policySearch every lender policy in the CreditPolicy library and get the exact wording back, cited.
list_lendersSee which lenders are covered before asking.
compare_lendersPut two to four lenders side by side on the same question.
assess_scenarioRun a whole deal across the panel and see who's likely to approve.
list_clientsFind any of your clients by name, business, email or ABN.
get_clientPull the full client file into the conversation — financials, people, companies, trusts, relationships and scenarios.
list_client_entitiesSee every separate person, company and trust linked to the client file.
create_client_entityAdd a separate person, company or trust without flattening it into the primary client.
link_client_entityReuse an existing person, company or trust in another client file without merging records.
create_client_relationshipRecord an explicit director, shareholder, trustee, beneficiary or other supported relationship.
update_client_entityUpdate an existing person, company or trust without replacing the rest of the record.
update_client_relationshipUpdate supported relationship details such as ownership percentage, primary flag or start date.
create_clientCreate a client from what you tell it — including income, debts and property.
update_clientUpdate an existing client — only the fields it's told to change.
add_client_financialsFill in a client's income, liabilities, property and business details later.
set_scenario_participantsChoose exactly which client records are involved in one scenario and in what role.
list_dealsSee what's on for a client, or across your whole book.
create_dealOpen a deal against a client, so the conversation is filed with it.
update_dealMove a deal along — submitted, approved, settled.
The policy library is read-only. It can create and update your own client files, separate people/companies/trusts, explicit relationships, scenarios and scenario participants, and save scenario runs — it can never delete policy content or access billing.
Setup
Connected in about a minute.
Get your access key
Add it to your assistant
- 1. claude.ai → Settings → Connectors → Add custom connector
- 2. Paste the server URL, click Connect.
- 3. Sign in to CreditPolicy and approve.
https://creditpolicy.ai/api/mcpNo key needed here — you sign in through CreditPolicy and approve, the same way you'd connect any other app.
Then just ask.
Tap any of these to copy.
Stop tabbing out
to check policy.
Connect once. Ask every policy question from inside the conversation you're already having.