Lokta MCP server

Ask Claude about your live loan book.

Servicing and collections teams can ask Claude what a borrower owes today, which loans sit in the 31-60 DPD bucket, what last month's disbursement report says, or who changed a repayment schedule. Claude gets each answer from your Lokta book through the Lokta MCP server. It signs in as the person asking, so it sees only what that person can see in Lokta.

The connector address is the same for every lender:

https://mcp.lokta.ai/mcp

What the connector does

The Lokta MCP server gives Claude 11 tools, and every one of them only reads. Claude can look up a loan, quote what a borrower would pay today, check a new loan against a product's limits, run a report or read the audit trail. It cannot post a repayment, change a schedule or edit any record.

Lokta's core calculates every figure Claude reports, including EMIs and repayment schedules, foreclosure amounts, penal charges, amounts due, outstanding balances and days past due. Claude receives each figure exactly as Lokta returns it.

Answers stay inside each person's Lokta permissions. Claude sees only the tools and records the signed-in person's role allows, and borrower details arrive masked: names show only their initials, and mobile and ID numbers only their last four digits. Your organization can turn masking off. Lokta refuses any request that contains an Aadhaar number.

MCP, the Model Context Protocol, is an open standard for connecting AI assistants to the tools people already use.

What you can ask

Ask Claude	What Lokta does
What does loan 000123 owe today, and how many days past due is it?	Looks up the loan
What would it take to close loan 000123 today?	Quotes the closing amount
Find the borrower whose mobile number is 98765 43210.	Finds the borrower
Show me the 31-60 DPD collections queue.	Lists the collections queue
Does ₹5,00,000 over 36 months fit our personal loan product's limits?	Checks the amount and tenure against the product's limits
Run last month's disbursement report.	Runs the report
Has day-end run today?	Reports the day-end status
Who changed the schedule on loan 000123 last week?	Reads the audit trail

Before you connect

Your organization uses Lokta, and a Lokta admin has turned on AI assistant access.
Your Lokta role includes the Use AI assistant permission.
You have your lender code and your Lokta username and password. A Lokta admin can tell you the lender code.
Your Lokta login doesn't use two-step sign-in, which the connector doesn't support yet.
You have a Claude plan with connectors. Free plans allow one custom connector. On Team and Enterprise plans, an owner adds Lokta for the organization first.

Connect Lokta to Claude

Free, Pro and Max plans

In Claude, open Customize > Connectors.
Select Add custom connector. In some layouts it sits under a + button.
Name it Lokta and enter the URL https://mcp.lokta.ai/mcp.
Enter the client ID. If the dialog shows Advanced settings, open it, enter lokta-claude as the OAuth client ID and leave the client secret empty. If it asks you to choose settings instead, choose Sign in now, then Use your own OAuth client, enter lokta-claude and leave the secret blank. Choosing Use Claude's published identity works too.
Add the connector, select Connect, and sign in to Lokta.

The OAuth client ID:

lokta-claude

Team and Enterprise plans

An owner adds Lokta once for the whole organization:

Open Organization settings > Connectors.
Select Add, then Custom. If Claude asks for the connector type, choose Web.
Enter the URL https://mcp.lokta.ai/mcp.
Enter lokta-claude as the OAuth client ID, under Advanced settings or as Use your own OAuth client, depending on the dialog. Leave the secret empty, then select Add.

Each member then opens Customize > Connectors, selects Connect next to Lokta, and signs in with their own Lokta login.

In a conversation

Select + in the message box, choose Connectors, and switch Lokta on. Then ask your question.

Claude Code

claude mcp add --transport http lokta https://mcp.lokta.ai/mcp

Then run /mcp in Claude Code, choose lokta, and sign in. Claude Code needs no client ID.

Other MCP clients

Other MCP clients that sign in with OAuth can use the same address. If one fails to connect, tell us its name at support@lokta.ai.

Signing in

Lokta opens its sign-in page in your browser.

Enter your lender code and select Continue. Once you have signed in, your browser remembers the code for a year. To switch lenders, select change next to the lender's name.
Enter the username and password you use in Lokta, and select Sign in.

Your organization's Lokta platform checks your password. The sign-in service passes it on and never stores it. After a stretch without use, Claude asks you to sign in again.

For Lokta admins

A Lokta admin turns AI assistant access on or off for the whole organization in Lokta's Setup, with the setting mcp-connector-enabled. It starts switched off. While it is off, nobody at your organization can use the connector, whatever their role.

The Use AI assistant permission decides who can use it. Add it to the roles that need it in Setup > Roles (its code is USE_AIASSISTANT). No role has it until you add it. Each person still sees only the tools and data their own role allows.

Disabling a user in Lokta stops their AI assistant access from their next question.

Lokta records every sign-in and every failed sign-in, with the lender code, username and network address, and keeps those records for 90 days. Lokta also logs every request the connector makes, in your organization's own Lokta database: who asked, when, what was requested, the outcome and the network address. Search terms in that log are stored masked, and admins with the READ_AGENTACCESSLOG permission can review it.

Repeated wrong passwords lock a login for 15 minutes. Sign-ins from one network are limited too: past the limit, that network waits 10 minutes.

People can disconnect Lokta at any time from Customize > Connectors in Claude.

Data and privacy

The connector reads your organization's Lokta data only when a signed-in person asks Claude a question, and only what that person's role allows. Your organization stays the data controller, and Lokta processes the data on its instructions. Once Claude has an answer, your organization's or the user's own terms with Anthropic apply to it. Section 13 of the privacy policy has the details.

Troubleshooting

On the sign-in page	What to do
We couldn't sign you in. Check your lender code, username and password.	Check all three. The username and password are the ones you use in Lokta.
Lender codes use only letters, numbers and dashes.	Check the lender code. It has no spaces or other symbols.
Too many attempts. Try again in 15 minutes.	Wait 15 minutes. Repeated wrong passwords lock the login for that long.
Too many sign-ins from your network. Try again in 10 minutes.	Wait 10 minutes. Colleagues on one office network signing in at the same time can cause it.
Your lender hasn't turned on AI assistant access.	Ask a Lokta admin to turn it on.
Your Lokta role doesn't include Use AI assistant.	Ask a Lokta admin to add the permission to your role.
Change your password in Lokta first, then come back.	Sign in to Lokta, change your password, then connect again.
Your Lokta login uses two-step sign-in.	The connector doesn't support two-step sign-in yet, so this login can't connect.
Lokta didn't answer. Try again in a minute.	Try again. If it keeps happening, write to support@lokta.ai.
Two Lokta logins at your lender differ only by capital letters.	Ask a Lokta admin to rename one of the two logins.
You're already signed in to Lokta as	Another Lokta login is open in this browser. Sign out with the link on that page, or connect from a private window.

In Claude	What to do
Claude asks you to connect Lokta again.	Your sign-in has ended. Select Reconnect next to Lokta in Customize > Connectors and sign in.
Claude answers without using Lokta.	Switch Lokta on for the conversation from + > Connectors, and name the loan, report or queue you mean.
Lokta refused a request that looks like an Aadhaar number.	Search for the borrower by name or mobile number instead, or ask for the loan by its loan account number.
An answer stops at 50 rows.	Ask a narrower question.

Support

Write to support@lokta.ai with your lender code, what you asked and roughly when. Never send your password.

To report a security vulnerability in the connector, write to support@lokta.ai with "Security" in the subject. We look into every report.

If your organization doesn't use Lokta yet, talk to us.