ecourts-mcp-server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ecourts-mcp-serverlookup case CS(OS) 123/2024 in Delhi High Court"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ecourts-mcp-server v1.2.0
An MCP (Model Context Protocol) server that connects LLMs to the EcourtsIndia Partner API v1.3, enabling AI agents to search Indian court cases, retrieve orders, read cause lists, and access AI-generated summaries.
Tools (9 total)
Tool | Description | Billing |
| Full case detail by CNR — parties, orders, IAs, notices, documents, hearings, FIR, linked cases, file AI status, case AI analysis | Per-request |
| Workflow tool — find a case by human-readable number (e.g. "CS(OS) 123/2024") instead of CNR, returns full details | Per-request |
| Rich search with 30+ filter params, year filters, date ranges, faceted aggregations | Per-request |
| Download order PDF with metadata (certified true copies) | Per-request |
| Extracted order text + pre-computed AI analysis (summary, outcome, key points) | Per-request |
| Browse state → district → complex → court hierarchy | Free |
| Search cause list entries across all courts | ₹1/request |
| Available cause list dates | Free |
| Queue a fresh scrape of case data | Per-request |
Related MCP server: CourtAPI MCP Server
Quick Start
npm install
npm run build
export ECOURTS_API_TOKEN="eci_live_your_token_here"
npm startDeployment
Docker
# Build
docker build -t ecourts-mcp-server .
# Run
docker run -d \
-e ECOURTS_API_TOKEN=eci_live_your_token_here \
-p 3000:3000 \
ecourts-mcp-server
# Health check
curl http://localhost:3000/healthDocker Compose
# Set your token
export ECOURTS_API_TOKEN=eci_live_your_token_here
# Start
docker compose up -d
# Verify
curl http://localhost:3000/healthCloud Deployment
The Docker image works with any container platform:
AWS ECS / Fargate — Use the health check endpoint at
/healthGoogle Cloud Run — Set
PORT=8080(Cloud Run default), server auto-adaptsAzure Container Apps — Standard HTTP container deployment
Railway / Render / Fly.io — Push the Dockerfile, set
ECOURTS_API_TOKENin secrets
The image runs as a non-root user, includes a HEALTHCHECK, and defaults to HTTP transport on port 3000.
Claude Desktop (stdio)
{
"mcpServers": {
"ecourts": {
"command": "node",
"args": ["/path/to/ecourts-mcp-server/dist/index.js"],
"env": {
"ECOURTS_API_TOKEN": "eci_live_your_token_here"
}
}
}
}Claude Code (stdio)
claude mcp add ecourts -- node /path/to/ecourts-mcp-server/dist/index.jsRunning Tests
npm test # 110 unit tests via vitest
npm run test:integration # 24 integration tests (requires ECOURTS_API_TOKEN)
npm run test:all # bothTests cover: query parameter serialization, all formatting functions, facet rendering, all 14 API error code branches, schema boundary validation, safeHandler wrapper, truncation, date validation, and typed fields. Integration tests cover court structure hierarchy, case search with filters/sort/years, case detail, order metadata, cause list search by date, case refresh, and error scenarios.
CI/CD
The .github/workflows/ci.yml pipeline:
Build & test on Node 20 and 22 (on push/PR to main)
Docker build + health check on push to main
Architecture
src/
├── index.ts # Entry point, transport (stdio/HTTP), health endpoint
├── constants.ts # Base URLs, character limits
├── types.ts # Full TypeScript interfaces for all API responses
├── schemas/index.ts # Zod input validation with date regex enforcement
├── services/
│ ├── api-client.ts # HTTP client, binary download, repeated-key array serializer, error handling
│ └── formatting.ts # Markdown formatters for case, search, causelist, order
└── tools/index.ts # 9 tool registrations with MCP annotationsEnvironment Variables
Variable | Required | Description |
| Yes | EcourtsIndia Partner API bearer token |
| No |
|
| No | HTTP port (default |
Changelog
v1.2.0 (current)
Code Quality:
Eliminated all unsafe type casts —
linkCases,subordinateCourt, andfirDetailsare now proper typed fields onCourtCaseDataCauseListEntryexpanded withpetitionerAdvocates,respondentAdvocates,internalCaseNo,dateCreated,dateModifiedProper
AvailableDatesResponseandCaseFileSummarytypes replace inline anonymous typesAll date parameters validated with
YYYY-MM-DDregex at schema level
New Features:
ecourts_lookup_case— workflow tool that finds cases by human-readable number (e.g. "CS(OS) 123/2024") instead of CNROrder file status in case detail —
ecourts_get_casenow shows which orders have AI analysis available with summary previewsHealth check endpoint —
GET /healthfor load balancers and container orchestratorsError-safe HTTP transport — Express handler now catches errors instead of hanging
ecourts_get_orderPDF download — returns order PDF as embedded resource with metadata (filename, file size) extracted from HTTP headers
Deployment:
Multi-stage Dockerfile (22MB Alpine image, non-root user, HEALTHCHECK)
docker-compose.yml with health check and token validation
GitHub Actions CI (Node 20/22 matrix, Docker build verification)
Test suite expanded to 110 unit tests + 24 integration tests
v1.1.0
Fixed array parameter serialization (courtCodes, caseTypes, etc.)
Added
isErrorflag on MCP error responsesComplete error code handling (11 API error codes)
15+ new search parameters (year filters, date ranges, categories, bench types)
Facet counts in search output
Comprehensive case detail formatting (all sections)
v1.0.0
Initial release with 8 tools covering all EcourtsIndia Partner API endpoints
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rithik-cmyk/ecourts-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server