Skip to main content
Lexful can be exposed to AI agents and tools via the Model Context Protocol (MCP). This lets you use Lexful capabilities from compatible agent runtimes without hand-writing all of the plumbing.
MCP support for Lexful is currently in preview. The core endpoint is stable, but client-specific behavior may change and some integrations have not been fully tested yet.
This page gives a high-level overview of how Lexful works with MCP and the endpoint you will use to connect.

​
MCP endpoint

Your MCP endpoint is: 
https://api.us.lexful.app/mcp/{YOUR_ACCOUNT_ID}
Your account ID is the same value used for Lexful API access (for example, in the X-Account-ID header). You can find it in your account settings. Authentication to this endpoint is handled via OAuth. On first connection from a compatible MCP client, you will be prompted to authorize access. If you are using a hosted demo environment, your team may provide a preconfigured demo account ID and corresponding MCP endpoint.

​
What MCP enables

At a high level, MCP allows you to:
  • Describe Lexful operations as tools that an AI agent can call.
  • Configure authentication and base URLs once, then reuse them across tools.
  • Standardize how agents access Lexful alongside other systems.
You can connect Lexful to:
  • Chat interfaces that expose MCP via Connectors or Apps UIs (for example, claude.ai or ChatGPT).
  • Developer tools that support raw MCP JSON config (for example, Cursor, Claude Desktop, or IDE extensions).
In chat UIs, you typically paste the MCP URL into a connector form and complete OAuth in the browser. In developer tools, you usually add a small JSON block to a config file or settings panel.

​
Where to go next