Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.loqate.com/llms.txt

Use this file to discover all available pages before exploring further.

The lqt binary includes a built-in MCP (Model Context Protocol) server that exposes Loqate verification as tools that AI agents can call directly. This means your agent can verify addresses, emails, and phone numbers without shelling out to the CLI — the MCP client handles tool invocation natively.

​
Two modes

ModeCommandBest for
Stdiolqt mcpLocal agents — Claude Code, Cursor, VS Code. Communicates over stdin/stdout.
HTTPlqt mcp --http :8080Hosted deployments. Includes per-IP rate limiting, request logging, and a /health endpoint.

​
Setup by client

Add Reach as a local MCP server:
claude mcp add loqate -- lqt mcp
Set your API key as an environment variable in your shell profile, or pass it in the MCP config:
.claude/settings.json
{
  "mcpServers": {
    "loqate": {
      "command": "lqt",
      "args": ["mcp"],
      "env": {
        "LOQATE_API_KEY": "your-key-here"
      }
    }
  }
}
Verify the connection:
claude mcp list

​
Remote MCP server

If you prefer not to install the CLI, you can connect to the hosted MCP endpoint: 
https://reach.prod.fabric.gbgplatforms.com/mcp

claude mcp add --transport http loqate-reach https://reach.prod.fabric.gbgplatforms.com/mcp
The remote MCP server (HTTP mode) exposes 6 of the 9 tools. parse_address, set_policy, and recommend_policy are only available in stdio mode. See Available Tools for the full breakdown.
When using the remote MCP server, your API key can be configured at the organization level (Claude Desktop, Claude Code, Cursor) or passed per-session. See Configuration for details.

​
HTTP mode

For hosted or shared deployments, run the MCP server in HTTP mode: 
lqt mcp --http :8080
HTTP mode adds:
  • Per-IP rate limiting
  • Request logging
  • /health endpoint for load balancers and monitoring