You can run a working litigation practice on the eCourtsIndia MCP with just Claude, the MCP connection, and one shared sheet. It handles the tracking half of practice management, cause lists, new orders and stalled matters, and the whole setup takes a single afternoon rather than a month of onboarding. If you would rather not build anything, the AI Clerk on ecourtsindia.com does the same tracking for you, with WhatsApp and email alerts.
Last updated: 16 November 2026
TL;DR: Pair Claude (desktop or web) with the eCourtsIndia MCP and one sheet of CNRs. Ask five plain-English questions a week (what is listed tomorrow, what orders landed, what has stalled, what opposing counsel is doing, how the bench has ruled) and you have a solo-practice tracking system in an afternoon. Cause-list data covers district and taluka courts; High Court dates come from the refreshed case record. It will not bill, file or give advice; for that you still buy practice-management software.
Paid litigation-management platforms such as Provakil, Komlit (from Lexplosion) and MyKase do credible work, and they add things this post will not give you: billing, client portals, conflicts checks and firm-wide reporting. Pricing depends on seats and features, and rolling one out across a chamber takes time.
A solo advocate with 140 pending matters, a Delhi High Court roll number, and a weekly WhatsApp dump to the client list can get the tracking half of what those platforms offer in one afternoon. The stack is Claude, the eCourtsIndia MCP, and one shared Google Sheet. The MCP is run by eCourtsIndia (ecourtsindia.com), an independent, non-government platform, and sits on top of 30 crore+ case records from the Supreme Court, all 25 High Courts, district and taluka courts in all 36 states and union territories, and 18 tribunal and commission types, plus a statute book of 10,000+ Acts. Cause-list search covers district and taluka courts only. This post shows how.
How can an advocate track all their cases in one place with AI?
Keep your CNRs in one sheet, connect Claude to the eCourtsIndia MCP, and ask the same few questions every week: what is listed, which orders arrived and which matters have stalled. Claude checks each case against the court record and answers in one table. One limit to know up front: the MCP only reads court data. Reading your Google Sheet, posting to Notion or Slack, creating calendar entries or running on a timer each need their own Claude connector or an automation tool.

The five questions that run a litigation practice
Every matter-managing advocate asks the same five questions every week. The MCP answers each with one prompt. (Your CNR, Case Number Record, the 16-character identifier the court assigns each case, is the key the MCP uses to track every matter.)
| Question | MCP approach |
|---|---|
| What is listed tomorrow across my matters | search_causelist with your advocate name, sorted by courtroom, or check_cnr_causelist with up to 100 CNRs (district and taluka courts; High Court dates from the refreshed case record) |
| What orders came in this week | bulk_refresh_cases with your CNR list, filter orders in last 7 days |
| Which matters have not moved in 60 days | bulk_refresh_cases, compare lastHearingDate to today |
| What is opposing counsel doing on her other matters | search_cases with advocates="Opposing Counsel" |
| What has the bench ruled on similar matters recently | search_cases with the judge’s name, hasOrders=true, last 6 months (see how to research a judge’s case history) |
The filter names in that table are shorthand. You do not memorise parameters: you describe the slice you want (an advocate, a date window, only matters with a fresh order) and Claude assembles the call. Think of hasOrders or lastHearingDate as the questions you ask, not switches you flip.
For the first question there is a faster route than searching by your name: check your own CNRs. The check_cnr_causelist tool takes up to 100 CNRs from your docket in one step and tells you which are listed for an upcoming hearing, where and for what. Developers can call the same check on the partner API as POST /api/partner/causelist/cnr/batch (a single case is a one-element array; see the complete eCourtsIndia API guide). At the time of writing (October 2026) it is billed per CNR: ₹0.30 on pay-as-you-go or ₹0.10 on an Enterprise plan.
How do you set it up?
Open Claude on desktop or at claude.ai and add the eCourtsIndia MCP as a connector: it takes about 90 seconds, and our MCP 101 guide and step-by-step guide to connecting the eCourtsIndia MCP to Claude walk through it, with setup notes on ecourtsindia.com/api/mcp. A free account comes with ₹200 in credits (October 2026). Put your CNR list in a Google Sheet with columns for Matter, Client, Counsel Assigned, Exposure and Last Update. That sheet is your docket. Either paste the CNR column into Claude when you run a prompt, or connect Google Sheets to Claude as a separate connector so it can read the sheet itself.
A full week on the MCP
A practice does not run on a single Monday prompt. It runs on a rhythm. Here is a routine that fits around hearings rather than competing with them: a heavy pull at the start of the week, light order checks in the middle, and a portfolio review on Friday before you sign off.
Monday: the cause-list pull
Monday is for knowing the week ahead. You want every listing where your name appears, grouped so you can plan travel between courtrooms and hand juniors their briefs. The setup is one instruction.
Pull the cause list for this week across my district and taluka matters. Search by my advocate name with search_causelist (district/taluka only; High Court and tribunal lists are not in this dataset). For High Court matters, refresh the CNRs on my sheet and read nextHearingDate from case detail instead. Group district results by date, then by courtroom. For each listing give me the case name, the stage, and the CNR. Put tomorrow's listings at the top.
The cause-list data behind this prompt covers upcoming lists for 8,000+ district and taluka courts; how far ahead a court’s lists run varies, typically several days to a few weeks. High Court and tribunal lists are not in it. If you are new to the format, how to read an Indian cause list explains stages such as charge, evidence and miscellaneous.
Mid-week: the order check
Wednesday and Thursday are for catching what moved. Benches upload orders on their own schedule, so a matter heard Tuesday may only surface its order on Thursday morning. A light, targeted refresh keeps you from being the last to know. When you need the full paper trail on a single matter rather than a portfolio sweep, list_case_orders returns every order and judgment on that case, newest first, and pairs naturally with get_order_markdown when you want the text of a particular one.
Refresh only the matters that were listed in the last three days. For each one, tell me whether a new order has been uploaded since Monday. If yes, give me a two-line plain-English summary and the next listing date. If a matter was listed but shows no order yet, flag it as "awaiting order".
Friday: the portfolio review
Friday is for the matters nobody is talking about. The cases that quietly stall are the ones that turn into an angry client call three months later. The portfolio review surfaces them before they fester. If a matter shows a past next date and no order, check whether the judge was on leave or the court on vacation before you chase the registry.
Review my whole docket from the Google Sheet. Refresh all CNRs (in batches of 50). Flag every matter with no movement for 60 or more days. For each flagged matter, give me the last recorded event and how many days ago it was. Sort the flagged list by exposure, highest first, using the Exposure column in my sheet. End with a one-line count of healthy vs stalled matters.
If your Claude plan or an automation tool supports scheduled runs, and you have connected Google Sheets and Notion as well, the Monday pull can run without you. The docket sheet is read, every CNR refreshed, and the summary posted to your team space at a fixed time, as in this routine:
Every Monday at 07:00 IST: 1. Read the CNR list from my Google Sheet. 2. Refresh all of them via bulk_refresh_cases. 3. For each CNR, report: last order date, last hearing date, next listing, current status. 4. Flag any matter where no movement for 60+ days. 5. Flag any matter with a new order in the last 7 days. 6. Summarise in a table. 7. Paste the table into my shared team Notion at /litigation/weekly.
One practical limit to build into the routine: a single bulk_refresh_cases call handles up to 50 CNRs, so a 140-matter docket is refreshed in three batches rather than one, and Claude chunks the sheet for you. A refresh queues a fresh pull from the court’s servers and usually lands in 2 to 10 minutes, so read the results after the refresh has landed rather than straight away. If you would rather watch the whole portfolio as one unit than refresh it list by list, the MCP also has a monitor_portfolio tool that checks a whole CNR list in one call. All of these, check_cnr_causelist, bulk_refresh_cases, list_case_orders, and monitor_portfolio, are among the MCP’s 41 tools. 13 of those tools never consume credits, mostly court-structure lookups, live codes and status checks; the eight statute-book tools (search_statute, lookup_provision, map_provision and the rest) are charged per section like the rest of the API. The DIY route gives you a consolidated view you assemble yourself; if you would rather log in to one, that is what the AI Clerk’s case tracking on ecourtsindia.com does, covered below.
For High Court and district court matters, that per-case pull now surfaces richer detail than it used to. Alongside the order, hearing, and listing dates, recent records expose fields like the e-filing number and date, filing type, litigant type, and structured parties, and for district matters the interlocutory applications, transfers, and full hearing history. These appear on the case page itself; you do not have to ask for any of it, and when a court publishes it, the refresh captures it.
Ten minutes from Monday 7 am, and the team stand-up has an agenda.
What a consolidated weekly docket looks like
The point of the Monday pull is that you stop opening a dozen court websites. The output is one table for the whole week, built from two sources. District and taluka rows come straight from the cause-list search, with the courtroom and stage. High Court rows come from the next hearing date on each refreshed case record, because cause-list search does not cover High Courts or tribunals. A worked output, with illustrative names, reads something like this.
| Date | Court / Room | Matter | Stage | CNR (last 4) | Source |
|---|---|---|---|---|---|
| Tue | Delhi High Court | Client A (writ) v. Union of India | Next date per case record | …4471 | Case record |
| Tue | Delhi High Court | Client B Estates Pvt Ltd v. DDA | Next date per case record | …8820 | Case record |
| Wed | Saket, Court 3 | State v. Client C | Charge | …1093 | Cause list |
| Thu | Patiala House, Court 7 | Client D recovery suit | Evidence | …5512 | Cause list |
| Fri | Tis Hazari, Court 21 | Client E v. BuildWell Pvt Ltd | Summons | …3076 | Cause list |
Two High Court matters on the same morning means one trip, not two. A charge hearing and an evidence hearing on consecutive days means you brief the right junior for each. The consolidation is the whole value: the information always existed on the public record, but no human was going to assemble it by hand every Monday. If you want to see the raw district lists behind a pull, the eCourtsIndia cause list page carries the same daily data.
Integrations you will want in week two
Once the pulls are reliable, the next gain is getting the output to where your team and clients already are.
- Push the weekly summary to a shared Slack or WhatsApp channel so juniors and partners see the same docket you do.
- Create a Google Calendar event for every “listed tomorrow” row, with the case name and courtroom in the title and the CNR in the notes.
- Generate a short client-facing WhatsApp line per matter, “Your case is listed on Thursday at Patiala House for evidence,” and review the batch before it goes out.
- Maintain a separate CSV for audits, so you can demonstrate compliance with your firm’s client-communication policy.
The WhatsApp client update is the one that earns goodwill fastest. Clients rarely chase you because they have nothing to chase; a two-line note the evening before a listing tells them you are on it. Keep a human in the loop on those messages. The MCP drafts, you approve, the client receives. Never wire an automated send straight to a client list without a review step. If you only need alerts for yourself, you do not have to wire anything: case alerts on ecourtsindia.com send a WhatsApp and email message when a tracked case changes.
DIY on the MCP, AI Clerk, or practice-management software?
They sit at different points in a practice’s life. The useful comparison is where each one earns its keep.
| Capability | DIY MCP stack | AI Clerk (no code) | Paid platform |
|---|---|---|---|
| Cause-list and order tracking | Yes, on the public record | Yes, mapped cases are checked daily | Yes, often with denser daily coverage |
| Change alerts | Yes, one prompt, or whatever you wire up | WhatsApp and email on a new order, filing, IA or hearing date | Yes, dashboards and reminders |
| Documents and questions per client | Only what you keep in your own drive | Files and cases organised per client, with an AI clerk to ask | Usually, varies by product |
| Time capture, billing, trust accounting | No | No | Yes |
| Conflicts checking | No | No | Yes |
| Setup time | An afternoon | Minutes per client | Plan for an onboarding period |
| Cost | Your Claude plan plus MCP credits from a prepaid wallet (₹200 free on signup). Pay-as-you-go: about ₹0.15 per case refresh, ₹1.50 per case detail, ₹3 per cause-list search | Free plan, plus ₹100 a month via the Chrome Extension; ₹250 + GST a month for 250 credits; tracking ₹5 per case per 30 days, alerts ₹0.50 each, AI order summary ₹2 | Varies by seats and features |
The paid platforms are not overpriced; trust accounting and conflicts checking are hard problems and worth paying for once they matter. The MCP stack is not a toy either: for a solo or a two-person chamber whose pain is tracking, not billing, it does the job that keeps clients calm. If you mainly want every pending case on one screen, see how to track all your pending court cases in one place.
If you like the tracking but not the building, the AI Clerk is the no-code version of this stack. You create a client, map its cases (or import them in bulk from the eCourts Services app), switch on daily monitoring, and changes reach you by WhatsApp and email. Our AI Clerk walkthrough covers the five steps, and the full rate card is on the pricing page. Credits never expire. Between hearings, the Chrome extension and the Android and iOS apps put the same case records in your browser and on your phone. General counsel running a larger book should read our portfolio monitoring playbook, which scales this routine to hundreds of matters.
Security and data handling
A practice tool touches client information, so a few habits are worth setting on day one. The case data the MCP reads is already public record on the eCourts system, but your docket sheet, your client phone numbers, and your internal notes are not, and they deserve care.
- Keep the docket sheet on an account you control, with sharing restricted to the people who need it. The CNR list itself is low-risk; the client and exposure columns are not.
- Store CNRs and case numbers in the sheet. There is no reason to keep client contact details in the same place you run automated pulls if you can avoid it.
- Treat any client-facing message as a draft until a human approves it. This is a security control as much as a courtesy, since it catches a wrong number or a mismatched matter before it leaves.
- If your firm has a client-communication policy, keep the audit CSV so you can show what was sent, to whom, and when.
- Review who has edit access to the shared sheet every few months. Stale access is the most common quiet leak in a small chamber.
What the MCP will not do
An honest tool comes with an honest list of limits. The MCP reads and organises the public court record. It does not replace your judgment, and there are things it simply cannot do.
- It does not file anything. No e-filing, no vakalatnama, no replies. It watches the record; it does not write to it.
- It does not capture your billable time or raise an invoice. If billing is a revenue leak, that is a paid-tool job.
- It is only as current as the court’s own uploads. If a bench has not uploaded an order, the MCP cannot show you an order that is not there yet.
- It does not give legal advice or decide strategy. A plain-English summary of an order is a starting point for your reading, not a substitute for it.
- It does not guarantee completeness on records the public system itself does not expose. Always confirm anything consequential against the source.
How this compares to paid products
Paid products have real advantages. Time capture. Billing. Trust accounting. Client portals. Conflicts checking. Document assembly. Firm-wide reporting. You will outgrow this DIY stack when your practice becomes a team of five or more, when billable-hour capture becomes a revenue issue, or when a client audit demands an immutable log. That is fine. The MCP stack gets you from zero to a working practice tool. Pay for the rest when you need it.
Where to start
You do not need a year-long procurement cycle to get your practice organised. Start with one matter. Paste its CNR into Claude and ask, “What happened in this case in the last year? Explain in plain English.” If you want a public matter to test on before you use a client’s, try SCIN010064302008 (CCE Pune v. Tata Motors Ltd, Supreme Court of India). If the answer is useful, expand to ten matters, then to your whole docket. Our CNR Decoded post explains how the 16-character identifier works. While you are setting up, claim your listing in the verified advocate directory: it is free and verified, and it is where litigants looking for counsel find you.
Further reading: The 5 AM Cause List Problem, Case Status Dictionary, the general counsel portfolio playbook.
Sources
- eCourtsIndia MCP tool catalogue and server notes (tools, limits, cause-list coverage): mcp.ecourtsindia.com/tools and mcp.ecourtsindia.com/llms.txt
- eCourtsIndia API and MCP pricing (October 2026): ecourtsindia.com/api/pricing
- eCourtsIndia AI Clerk pricing (October 2026): ecourtsindia.com/pricing
Frequently Asked Questions
How can an advocate track all their court cases in one place?
Keep a list of your CNRs and use a tool that checks each case against the court record. On eCourtsIndia you can either add cases to AI Clerk, which sends WhatsApp and email alerts when something changes, or connect Claude to the eCourtsIndia MCP and ask it each week what is listed, which orders arrived and which matters have stalled.
Can Claude check my cause list for tomorrow?
Yes, for district and taluka courts. Connected to the eCourtsIndia MCP, Claude can search cause lists by your name as advocate, or check up to 100 of your CNRs at once, and tell you where and for what each matter is listed. High Court cause lists are not covered, so for High Court matters it reads the next hearing date from the refreshed case record.
How do I find matters that have not moved for months?
Refresh your whole CNR list and compare each matter’s last hearing or order date with today. With the eCourtsIndia MCP, one prompt can refresh up to 50 CNRs per batch and flag anything with no movement for 60 days or more, sorted by value or priority. A refresh usually lands in 2 to 10 minutes, so read the results after that.
What does it cost to track cases with the eCourtsIndia MCP?
Connecting is free and new accounts get ₹200 of credits. As of October 2026, on pay-as-you-go a case refresh costs about ₹0.15, a case detail ₹1.50 and a cause-list search ₹3, while Enterprise plans pay a third of that. Court-structure tools are free; statute look-ups cost ₹0.15 per section. You also need your own Claude or ChatGPT plan.
Do I need to code to use the MCP for my practice?
No. You add one URL to Claude as a custom connector and then ask questions in plain English. If you want Claude to read your docket from Google Sheets, post summaries to Notion or Slack, or run on a schedule, those need separate connectors or an automation tool. If you want no setup at all, AI Clerk on eCourtsIndia does case tracking with alerts.
Is client data safe when I run these pulls?
The court data the MCP reads is already public record. Your docket sheet, client phone numbers and notes are not, so keep the sheet on an account you control, restrict who can edit it, keep client contact details out of the sheet you run pulls against, and treat every client-facing message as a draft until a person approves it.
What can’t an AI tracking setup do for a law practice?
It cannot e-file, draft vakalatnamas, record billable time, raise invoices, check conflicts or give legal advice. It only reads the public court record, so it is as current as the court’s own uploads. Summaries of orders are a starting point for your own reading. Paid practice-management software is still the right choice once billing and team workflows matter.



