LexisNexis MCP Server & Agent Skill

What is the LexisNexis API, and what can an agent read from it?

Licensed REST and Cognitive APIs with JSON: Protégé 'Ask' and 'Summarize' with citations, legal and news search and retrieval with alerts, CourtLink dockets, Lex Machina analytics and State Net legislation.

• API: Lexis APIs (Protégé API, REST APIs, CourtLink API, Lex Machina API, State Net API, Law360 API) (REST)
• Access: Partner or license program
• Authentication: OAuth 2.0

License-gated. Organizations request access through LexisNexis; once approved they get credentials and onboarding for the LexisNexis Developer Portal (dev.lexisnexis.com) with docs and a sandbox. Pricing depends on products and volume.

LexisNexis states its REST, Cognitive and Protégé APIs use OAuth authentication with role-based access, firm-wide throttling and audit logging. Grant types and endpoints are documented only inside the gated portal.

What can an agent read from LexisNexis?

• Protégé answers — 'Ask' and 'Summarize' return answers with citations grounded in primary law, secondary materials and Practical Guidance.
• Legal and news content — Search and retrieve legal and news content; set alerts for new content.
• Court dockets — CourtLink API: federal and state filings, docket updates and case tracking.
• Litigation analytics — Lex Machina API: judges, attorneys, parties, resolutions, damages and timing.
• Legislation and regulation — State Net API: bills, regulations, agency documents, ordinances and ballot measures.

What can an agent write to LexisNexis?

This skill only reads LexisNexis data; it documents no write calls, so an agent built on it cannot change a LexisNexis record.

Research queries and uploaded matter facts can reveal client strategy and are attorney work product; keep them confidential and out of shared logs.

How do I connect LexisNexis to an AI agent over MCP?

As of October 2026 we found no MCP server published by LexisNexis itself.

The practical path is to host a small MCP server that wraps the Lexis APIs (Protégé API, REST APIs, CourtLink API, Lex Machina API, State Net API, Law360 API), or to give the agent the calls directly with the SKILL.md below.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

For an API key or a service credential, one token connection at platform scope serves the whole organization; scope a connection to a single agent when that agent needs narrower access than the rest.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the LexisNexis agent skill do?

The LexisNexis skill is one SKILL.md file named iblai-connect-lexisnexis. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the LexisNexis SKILL.md

Save it as .claude/skills/iblai-connect-lexisnexis/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against LexisNexis' documentation on October 20, 2026. Test it against your own LexisNexis setup before you rely on it.

What can I ask a LexisNexis agent to do?

• “Summarize the leading New York cases on piercing the corporate veil since 2020, with citations”
• “Track new docket entries in the Acme v. Beta case in S.D.N.Y.”
• “How often does Judge Smith grant summary judgment in patent cases?”
• “Alert me to new state bills on biometric privacy”

How do I run a LexisNexis agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the LexisNexis MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

• AI agents for Legal — what ibl.ai deploys in this sector

Which ibl.ai agents work with LexisNexis data?

• Case Research — Legal
• Brief Drafting — Legal

Which ibl.ai platform skills does a LexisNexis agent use?

• /iblai-api-agent-mcp — MCP connectors for ibl.ai agents, end to end
• /iblai-vibe-agent-mcp — Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,…
• /iblai-api-agent-tool — Enable or disable an ibl.ai agent's tools via the platform API

What else should I know before connecting LexisNexis to an AI agent?

Which other data sources can an AI agent connect to alongside LexisNexis?

Which other Legal systems have a connector?

• Clio Manage — Legal practice management system
• Docusign eSignature — Electronic signature platform
• iManage Work — Legal document and email management system
• Ironclad — Contract lifecycle management system
• NetDocuments — Cloud legal document management system
• PACER — U.S. federal court records system
• RelativityOne — E-discovery and legal review platform
• Westlaw — Legal research platform

Every connector, grouped by sector, is on the connectors hub.