Litigation Portfolio Monitoring for General Counsel: A Claude + eCourtsIndia MCP Playbook

A listed Indian company with 1,800 live matters across nine states cannot rely on its panel counsel to email in every change. A bank with tens of thousands of Section 138 NI Act recoveries in district courts across the country cannot manually aggregate Monday updates. An NBFC with exposure in three tribunals plus eight High Courts cannot let a single case slip a deadline. The data layer that makes portfolio monitoring possible has been live and maturing for years. It now reaches across 32 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. The product wrapper that lets a General Counsel use it directly, in their own words, in their own Claude window, now also exists. This post is the playbook.

Last updated: 23 September 2026

A General Counsel can monitor an entire litigation portfolio by uploading a five-column CSV of CNR numbers into Claude, connecting the eCourtsIndia MCP, and running one Monday prompt. Claude queues a refresh of every case with bulk_refresh_cases, reads the refreshed records once they land, pulls the order narrative with get_case_with_latest_order, flags new orders and upcoming hearings, totals exposure by counsel, and produces a board-ready report in about ten minutes.

The one CSV you need

Five columns, nothing more. The CSV is the only thing a General Counsel has to maintain by hand, and most of it already lives in your matter tracker or a finance spreadsheet. The CNR number, the Case Number Record (a permanent 16-character ID the eCourts system assigns to every case nationwide), is the single key that links your internal record to the public court record, so it is the one column you cannot skip.

Column	Example
CNR	DLHC01XXXXXX2019 (use your own 16-character CNR)
Matter	XYZ v. Petitioner State
Exposure (INR)	2,50,00,000
Panel Counsel	Firm A
Business Owner	CFO office

Upload the CSV into Claude. Point Claude at the eCourtsIndia MCP (add https://mcp.ecourtsindia.com/mcp as a custom connector and click Connect). You now have everything needed for the weekly report. If you do not yet have the CNR for a matter, you can look it up by party name on eCourtsIndia and paste it into the sheet once. After that the number never changes for the life of the case.

The Monday morning prompt

The order of the prompt matters. You queue a refresh of the whole list in bulk first, read the refreshed records once they land, and then ask for the narrative only on the cases that actually moved. That keeps the run fast and the tool usage consistent with the way the MCP is built: one tool for many CNRs, a different tool for a single CNR.

Take the CSV I just uploaded.

1. Call bulk_refresh_cases on every CNR in the file, 50 per call, to queue a fresh pull from the court servers.
2. Check check_refresh_status until the refreshes have landed, then read the refreshed records with batch_get_case_details.
3. For any case that changed since last Monday, call get_case_with_latest_order to get the order narrative.
4. Flag any case with a new order since last Monday.
5. Flag any case where the next hearing is this week.
6. Flag any case that has moved to DISPOSED, DISMISSED, or ALLOWED.
7. For flagged orders, call get_order_ai_analysis to extract directions, stay conditions, and deposit orders.
8. Total outstanding exposure by panel counsel.
9. Produce a five-line executive summary, then a full table.
10. Save to /board/litigation/WK17 as a Word document.

Ten minutes to a complete Monday view. No legal ops engineer required. The same prompt runs every week with only the week number changed, so it becomes muscle memory rather than a project.

The MCP tools doing the work

Four MCP tools carry the weekly workflow, and the prompt above uses them in exactly this order.

• bulk_refresh_cases to queue a fresh pull from the court servers for a batch of CNRs in a single call. It handles up to 50 CNRs per call, so a large portfolio is swept in batches of fifty rather than one matter at a time. It does not return the new data itself: refreshes typically land within a few minutes, and check_refresh_status (free) tells you when they have.
• batch_get_case_details to read the refreshed records for the whole batch once they have landed, including status, last and next hearing dates and the latest orders.
• get_case_with_latest_order for the narrative text of what happened on a single CNR. Reach for this only on the cases that moved, not the whole list.
• get_order_ai_analysis for directions, stay conditions, and deposit orders pulled out of the order text.

There is also more to pick up than there used to be. High Court and District Court records now expose richer structured fields (e-filing number and date, filing and litigant type, structured parties, plus hearing-history and interim-application detail), so a weekly refresh surfaces more context on each matter, not just a change in status.

Those tools are only part of the kit. The eCourtsIndia MCP exposes 39 tools in all (v4.46). One of them, list_case_orders, lists every order and judgment on a case, so when a matter turns active you can pull its full order history rather than just the latest one. Another, monitor_portfolio, is built for exactly this job: programmatic portfolio monitoring across a set of cases, if you would rather watch the whole list from your own stack than orchestrate each refresh by hand. A third, check_cnr_causelist, is aimed squarely at the hearing line of the Monday prompt: hand it one to 100 CNRs in a single call and it answers whether each case is set down for an upcoming hearing and what it is listed for, without pulling and scanning each full cause list (the same check is exposed on the partner API as POST /api/partner/causelist/cnr/batch, billed per CNR checked at ₹0.30 pay-as-you-go or ₹0.10 on a subscription). Cause lists cover district and taluka courts only; High Court filters return zero. Nineteen tools never consume credits, including the seven statute-book tools. If you would rather not run any of this from Claude, the website route is the AI Clerk: map matters to a client and switch on alerts, covered in the Monday routine below.

The distinction is worth holding onto. If you loop get_case_with_latest_order over 1,800 CNRs you make 1,800 calls. If you start with bulk_refresh_cases, you sweep the list in batches of fifty (roughly three dozen calls for 1,800 matters) and then only drill into the handful that changed. Same answer, a fraction of the work. For the meaning of the status values you will see, our Case Status Dictionary is the reference.

A worked example: the weekly litigation board

Here is what the full table looks like when the prompt finishes. Take a slice of six matters from a larger portfolio. After the refresh lands, three of them moved this week and three did not. The flagged rows are the ones the General Counsel actually reads. The matters and CNRs below are illustrative and masked, so do not paste them into a search; use the CNRs from your own CSV.

CNR	Matter	Court	Next Hearing	Latest Order	Status	Flag
DLHC01XXXXXX2019	XYZ v. State	Delhi HC	24 Jun	Interim stay extended, deposit of 50 lakh ordered	Pending	Order + hearing this week
MHCC02XXXXXX2021	ABC Fin v. Borrower	Mumbai City Civil	02 Jul	Matter adjourned for evidence	Pending	None
KAHC03XXXXXX2020	State v. PQR Ltd	Karnataka HC	None	Petition dismissed	Dismissed	Disposed this week
TNHC04XXXXXX2022	LMN v. Authority	Madras HC	27 Jun	No change since last week	Pending	Hearing this week
GJHC05XXXXXX2019	RST v. Revenue	Gujarat HC	None	Appeal allowed in favour of company	Allowed	Favourable disposal
UPHC06XXXXXX2021	DEF Bank v. Guarantor	Allahabad HC	14 Aug	No change since last week	Pending	None

Three rows demand attention this week: a deposit order on the Delhi matter, a favourable appeal win in Gujarat, and a dismissal in Karnataka that closes exposure. The three quiet rows are noted and ignored. That triage, done in seconds, is the whole point. A General Counsel reads three lines instead of skimming sixty emails.

The board slide

The output from the weekly prompt is the raw material for a one-page board slide. A board does not want a case list. It wants three things, and the weekly table already contains all of them.

• Exposure movement week over week. The Karnataka dismissal and the Gujarat win both reduce live exposure, so the headline number falls. Quote the change, not the absolute.
• Disposals and favourable outcomes. Two cases closed this week, one in the company’s favour. That is the line that earns the legal team credit.
• Cases that need sign-off. The Delhi deposit order of 50 lakh needs a treasury decision before the next date. That is the only ask on the slide.

Everything else is noise for a board audience. A clean version reads: “Live exposure down this quarter on two disposals. One favourable High Court order. One deposit decision needs treasury sign-off by 24 June.” Three lines, sourced from the same run that produced the full table, with the underlying record one click away on eCourtsIndia if a director wants to verify it.

Governance and the audit trail

A General Counsel cannot adopt a tool they cannot defend in front of a board or a regulator. Three boundaries matter, and each one has a concrete control behind it.

• Audit trail. Every priced call is metered against the key or connection that made it, and usage shows in your eCourtsIndia API dashboard. Do not rely on that alone: keep your own run record. Save the week’s CSV, the prompt and the Word document to /board/litigation, so when someone asks how the board number was produced you can show exactly which CNRs were refreshed, when, and what came back.
• Access control. Give each person who runs the prompt their own key or their own OAuth connection rather than a shared service account, so activity is attributable to a named individual. Revoke the key or remove the connector on offboarding and the access is gone the same day.
• Data residency. Court records are public. The MCP serves public data. Nothing leaves your stack that was not already on the eCourts portal. You are reading the same orders any litigant or counsel could read, just aggregated and structured. That keeps the data-protection question simple: there is no confidential customer data flowing through the pipe, only public judicial record.

Taken together these three controls give a General Counsel a clean answer to the obvious internal questions: who can see it, what they did with it, and where the data came from. Each has a one-line answer, and each is backed by a record you can hand over.

Slotting it into matter management

The CSV is not a parallel system. It is a view that rides on top of whatever matter management you already run. Most legal teams keep their matters in a tracker that already holds the matter name, exposure, panel counsel, and business owner. Four of the five CSV columns are an export from that tracker, and the fifth, the CNR, is the one value you enrich once per matter. Export on Friday, run the prompt on Monday, and write the flagged outcomes back to your tracker as the week’s update.

That keeps the system of record where it belongs and uses the MCP purely as the live court feed. Your tracker still owns pleadings, invoices, and counsel instructions. The MCP owns nothing; it just answers the question “what changed in court this week” and hands the answer back in a form your existing process can absorb. Over a few weeks the Friday export and Monday run become a single habit rather than two separate tasks.

The Monday morning routine

In practice the whole thing collapses into a fifteen-minute slot before the rest of the office settles in.

• 8:45. Open Claude, drop in the CSV exported Friday evening.
• 8:47. Paste the standing prompt, change the week number, hit run.
• 8:57. The full table and five-line summary are ready. Read the flagged rows.
• 9:00. Forward the three-line board version to leadership and write the deposit decision into the ask list for treasury.
• 9:05. Write the flagged outcomes back into the matter tracker. Done for the week.

For anything that cannot wait until Monday, set up tracking in the AI Clerk on your eCourtsIndia dashboard: map the key matters to a client and switch on email and WhatsApp alerts. The clerk checks tracked cases every day and notifies you when a new order, filing, IA or hearing date appears (opt-in, credit-metered). Tracking costs ₹5 per case per month and each alert ₹0.50, and the free plan includes 50 credits a month; the full rate card is on the pricing page. The Monday run then becomes confirmation rather than discovery. Tracking covers High Court and district-court matters; NCLT and NCLAT cases are not trackable, so keep those on the weekly pull. A solo advocate version of this routine is in our run-your-practice-on-the-MCP guide.

When to pair with a CLM

If your organisation has contracts as complex as its litigation, a contract lifecycle management (CLM) product remains worth buying. Indian options worth a look include SpotDraft and Lexplosion for contract lifecycle work, and Provakil if you want litigation and contract management on one platform. The MCP is the live data feed. Your CLM is the system of record for pleadings, invoices, and panel counsel management. These are complements, not substitutes. Our migration piece for product teams goes into the architectural split.

Before a matter exists: screen counterparties with LegalCheck

Portfolio monitoring starts once a matter exists. The cheaper time to learn about litigation is before you sign: before onboarding a vendor, lending to a borrower or acquiring a company. LegalCheck screens a person or company against the eCourtsIndia court corpus, uses identity details such as a father’s name, addresses or directors to separate the right subject from namesakes, and returns a risk band with every match explained. A check costs ₹99, or ₹33 on an active subscription. It runs in the web app, as a partner API endpoint (POST /api/partner/legal-check) and as two MCP tools, submit_legal_check and get_legal_check, so the same Claude window that runs your Monday report can screen a new counterparty. Our LegalCheck launch post explains the method, the LegalCheck API guide covers integration, and teams building their own screening layer should read our legal due diligence engine guide.

What this means for GCs

You can get a board-ready view of your litigation portfolio every Monday at 9 am, in ten minutes, on prepaid API credits (a new account starts with ₹200 free). Start with a slice. Thirty matters. One region. One week. If the answer works, scale to the full portfolio. See our MCP 101 guide for install. For a click-by-click setup, follow our step-by-step guide to connecting the eCourtsIndia MCP to Claude. For Section 138 portfolios specifically, read our cheque bounce tracking post.

If your Monday board report still relies on Friday emails from eleven firms, it is not a report. It is a rumour.

Further reading: Case Status Dictionary, Case Type Encyclopedia.

Frequently Asked Questions