# How to connect HLR Lookup to Claude

```json
{
  "title": "How to connect HLR Lookup to Claude",
  "toolkit": "HLR Lookup",
  "toolkit_slug": "hlr_lookup",
  "framework": "Claude Cowork",
  "framework_slug": "claude-cowork",
  "url": "https://composio.dev/toolkits/hlr_lookup/framework/claude-cowork",
  "markdown_url": "https://composio.dev/toolkits/hlr_lookup/framework/claude-cowork.md",
  "updated_at": "2026-10-29T05:32:38.629Z"
}
```

## Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.
This guide walks you through the easiest and most secure way to connect your HLR Lookup account to Claude via Composio Connect, enabling it to validate customer numbers before sending messages, check carrier and portability for leads, process yesterday's phone list in bulk, and more such actions on your behalf without compromising your account security.
Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

## Also integrate HLR Lookup with

- [ChatGPT](https://composio.dev/toolkits/hlr_lookup/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/hlr_lookup/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/hlr_lookup/framework/atomic-agent)

## Connect HLR Lookup to Claude Cowork

### Connecting HLR Lookup to Claude Web, Desktop, and Cowork
Two ways to add the Composio connector. Pick whichever you prefer.
### 1. Add with one click
Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.
[Add to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp)
### Add manually
In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.
Click Add custom connector and paste in the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is the HLR Lookup MCP server, and what's possible with it?

The HLR Lookup MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your HLR Lookup account. It provides structured and secure access to phone validation, HLR status checks, network and portability data, credit balances, and bulk processing, so your agent can validate phone numbers, check live phone status, identify mobile networks, manage lookup batches, and monitor available credits on your behalf.
- Phone number validation: Have your agent validate up to 80 phone numbers at once and check their formatting and original network information.
- HLR and network checks: Direct your agent to run live HLR lookups or retrieve mobile network and number portability data for up to 80 phone numbers.
- Bulk lookup management: Let the agent create batches, upload phone numbers from JSON or CSV files, start or resume processing, pause work, and schedule a batch for a specific UTC time.
- Batch progress and results: Instruct your agent to list batches, check their current progress, and download completed results as CSV or JSON files.
- Credit balance monitoring: Have your agent check the remaining credit balance in your HLR Lookup account before running phone checks.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `HLR_LOOKUP_CHECK_PHONE_STATUS` | Check Phone Status | Run full HLR lookups for 1-80 phone numbers. This processes sensitive phone data and spends credits; optional status features can increase the cost. |
| `HLR_LOOKUP_CREATE_BATCH` | Create Batch | Create an empty persistent HLR_V2 batch. Creation has no documented charge and handles no phone data; later uploads persist sensitive phone data, and processing can spend credits. |
| `HLR_LOOKUP_DELETE_BATCH` | Delete Batch | Permanently delete one HLR batch and its results. This action is irreversible: never invoke it without explicit authorization, and download all needed results before deletion. It does not select a batch automatically. |
| `HLR_LOOKUP_DOWNLOAD_BATCH_RESULTS` | Download Batch Results | Download a completed batch's full, unpaginated CSV or JSON result export, including source phone values and sensitive HLR intelligence, as a file reference. Select the required format explicitly. |
| `HLR_LOOKUP_GET_BALANCE` | Get Credit Balance | Return the connected HLR Lookup account's remaining credit balance. This zero-credit read is the approved authentication check and does not process a phone number. |
| `HLR_LOOKUP_GET_BATCH` | Get Batch | Return metadata and current progress for one HLR batch. Use it to follow an asynchronous batch until status is COMPLETE. |
| `HLR_LOOKUP_LIST_BATCHES` | List Batches | List the connected account's HLR batches with their metadata and progress. The response reports provider offset and limit values, but the API documents no pagination inputs. |
| `HLR_LOOKUP_MNP_LOOKUP` | Run MNP Lookup | Look up network and mobile-number-portability data for 1-80 phone numbers. This processes sensitive phone data and spends credits; requesting the optional ported date is the only MNP feature that can add a surcharge. |
| `HLR_LOOKUP_PAUSE_BATCH` | Pause Batch | Pause processing one HLR batch. This action returns when the command is accepted and does not poll for a status change. |
| `HLR_LOOKUP_SCHEDULE_BATCH` | Schedule Batch | Schedule processing of one uploaded HLR batch at a UTC time. Scheduled processing of sensitive phone data can irreversibly spend credits, so never invoke this action automatically. This action does not poll for processing or completion. |
| `HLR_LOOKUP_START_OR_RESUME_BATCH` | Start or Resume Batch | Start or resume processing one uploaded HLR batch. Processing sensitive phone data can irreversibly spend credits, so never invoke this action automatically. This action returns when the command is accepted and does not poll for completion. |
| `HLR_LOOKUP_UPLOAD_BATCH_CSV` | Upload Batch CSV | Upload a CSV file of sensitive phone data into an empty HLR batch. The provider permits one source upload; repeating it on a populated batch is documented to fail. |
| `HLR_LOOKUP_UPLOAD_BATCH_JSON` | Upload Batch Phone Numbers | Upload 1-100,000 sensitive phone numbers into an empty HLR batch as a compact JSON array. The UTF-8 body must not exceed 2 MiB, and a populated batch cannot be uploaded again. |
| `HLR_LOOKUP_VALIDATE_NUMBER` | Validate Phone Numbers | Validate formatting and original-network information for 1-80 phone numbers without a live HLR lookup. It costs zero credits but still processes sensitive phone data. |

## Supported Triggers

None listed.

## Troubleshooting

### 1. Why does Claude not use the Composio connector for HLR Lookup?

The connector can show as connected, but Claude must use it in each HLR Lookup conversation.
- Click + at the lower left of the chat, or type /.
- Hover Connectors.
- Turn on Composio.
- Ask Claude to connect to HLR Lookup again.

### 2. Why does Claude show an MCP server error before HLR Lookup connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for HLR Lookup.
- Check that the connector URL is https://connect.composio.dev/mcp.
- Connectors run from Anthropic's cloud, so your device network is usually not the problem.
- Add the connector again from Customize > Connectors, then ask Claude to connect HLR Lookup.
- If it fails again, send the error and the ofid_ reference id to support@composio.dev.

### 3. Why does the HLR Lookup authorization link not work?

The Composio connector is one server. Your HLR Lookup account connects separately when Claude asks for it.
- If the browser does not open, or the link expires, ask Claude to retry the HLR Lookup connection.
- Composio creates a fresh HLR Lookup authorization link.
- Open that link in your browser and finish the HLR Lookup sign-in.

### 4. Why do HLR Lookup actions fail after they worked before?

The HLR Lookup connection can expire or lose permission.
- Ask Claude to inspect the HLR Lookup connection.
- If the connection is unhealthy, disconnect it when Claude prompts you.
- Reconnect the HLR Lookup account and retry the action.
- If Claude shows a permission prompt, approve it before Claude changes data in HLR Lookup.
- If the action still fails with a permission error, check that the connected account has that permission in HLR Lookup itself.

### 5. How do I switch to a different HLR Lookup account?

Claude can manage the HLR Lookup connection for you.
- Ask Claude to disconnect or delete the current HLR Lookup account.
- Ask Claude to connect HLR Lookup again.
- Open the new Composio authorization link for HLR Lookup.
- Sign in with the other HLR Lookup account in the browser.
- After the account connects, ask Claude to retry the HLR Lookup task.

### 6. Why is my HLR Lookup connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your HLR Lookup connection works in Claude Web, Desktop, and Cowork.
- In Claude Desktop, open Customize > Connectors.
- Next to Composio, click ⋮ and click Clear cache.
- If HLR Lookup tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
- On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect HLR Lookup.

## Creating MCP Server - Stand-alone vs Composio SDK

The HLR Lookup MCP server connects Claude Web, Desktop, and Cowork to your HLR Lookup account through Composio. Once connected, Claude can use the available HLR Lookup tools and triggers to complete tasks on your behalf.

## Complete Code

None listed.

## How to build HLR Lookup MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/hlr_lookup/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/hlr_lookup/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/hlr_lookup/framework/atomic-agent)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [1password](https://composio.dev/toolkits/_1password) - 1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anakin](https://composio.dev/toolkits/anakin_io) - Anakin is a web automation platform offering scraping, crawling, search, and browser automation. Use it to extract structured data, automate site tasks, and monitor web changes reliably.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Authyo](https://composio.dev/toolkits/authyo) - Authyo is a REST API service for passwordless authentication, OTP verification, session management, and transactional notifications. Use it to add secure login flows and user verification without building auth infrastructure from scratch.
- [AWS Marketplace MCP](https://composio.dev/toolkits/aws_marketplace_mcp) - AWS Marketplace MCP provides MCP access to AWS Marketplace's cloud software, data, and services catalog. Use it to discover, compare, and evaluate 30K+ AWS Marketplace listings faster.
- [Azure Monitor Activity Log](https://composio.dev/toolkits/azure_monitor_activity_log) - Azure Monitor Activity Log is Azure's service that records management and control-plane events for a subscription. Use it to audit changes, troubleshoot issues, and track resource operations across your Azure resources.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and HLR Lookup MCP?

With a standalone HLR Lookup MCP server, the agents and LLMs can only access a fixed set of HLR Lookup tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from HLR Lookup and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right HLR Lookup tools.

### Can I manage the permissions and scopes for HLR Lookup while using Tool Router?

Yes, absolutely. You can configure which HLR Lookup scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your HLR Lookup data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
