Skip to main content
LimitGuard’s MCP server is a standard remote Streamable HTTP endpoint at https://api.limitguard.ai/mcp. Any framework with a generic MCP client can connect to it directly - there is no LimitGuard-specific package or wrapper for LangChain, CrewAI, or the OpenAI Agents SDK. The examples below use each framework’s own remote-MCP client against that single URL.
For the raw MCP manifest (/.well-known/mcp.json), the tools it lists, and their pricing, see AI Agent Integration. This page is about wiring a framework’s MCP client to that server, not about the tool catalog itself.

Authenticating the MCP Connection

tools/list never requires authentication - any MCP client can discover LimitGuard’s tools without a key or a wallet. Calling a tool is different:
  • With an API key - send it as a Bearer token on the MCP connection: Authorization: Bearer lg_live_xxxxxxxxxxxxxxxxxxxx. A paid-tier key debits its prepaid balance per call, the same as REST.
  • Without a key - tools/list still works, and verify_wallet (wallet risk screening) is real and free ($0), callable with no key and no payment. Any other tool called without a key or a payment header gets back a JSON-RPC error naming the price and how to pay - there is no HTTP 402 on this transport, since a JSON-RPC error has no status-code channel.
Every example below shows the Bearer-token form; drop the headers entry (or the Authorization key inside it) to connect keyless.
Verify each framework’s MCP client API against its own current docs before shipping - these client classes change between minor releases. The imports and parameters below were checked against langchain-mcp-adapters 0.3.2, openai-agents 0.22.3, and crewai-tools 1.15.22.

LangChain

langchain-mcp-adapters turns any MCP server into LangChain tools via MultiServerMCPClient. Its streamable_http transport takes the URL and an optional headers dict - that’s where the Bearer token goes.
get_tools() opens a new MCP session per call by default. For an agent that calls LimitGuard tools repeatedly in one process, keep the MultiServerMCPClient instance alive and reuse it rather than constructing it per request.

OpenAI Agents SDK

The Agents SDK’s MCPServerStreamableHttp takes a params dict with url and headers, and is passed to an Agent via mcp_servers.
The async with MCPServerStreamableHttp(...) block opens the connection for the lifetime of the run and closes it on exit - construct the Agent inside that block, as shown.

CrewAI

crewai-tools ships MCPServerAdapter, built on the framework-agnostic mcpadapt library. Pass a plain dict with transport: "streamable-http" (hyphenated, unlike LangChain’s streamable_http) plus url and headers.
MCPServerAdapter connects as soon as it’s constructed and disconnects when the with block exits (or call .stop() manually if you construct it outside a context manager).

Next Steps

AI Agent Integration

The full MCP tool catalog, A2A, and x402 - including pricing per tool

Pay Per Call

Skip the API key entirely and pay per call with a USDC wallet