# How to integrate Codereadr MCP with Claude Code

```json
{
  "title": "How to integrate Codereadr MCP with Claude Code",
  "toolkit": "Codereadr",
  "toolkit_slug": "codereadr",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/codereadr/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/codereadr/framework/claude-code.md",
  "updated_at": "2026-05-12T10:07:02.660Z"
}
```

## Introduction

Manage your Codereadr directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Codereadr with

- [OpenAI Agents SDK](https://composio.dev/toolkits/codereadr/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/codereadr/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/codereadr/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/codereadr/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/codereadr/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/codereadr/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/codereadr/framework/cli)
- [Google ADK](https://composio.dev/toolkits/codereadr/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/codereadr/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/codereadr/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/codereadr/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/codereadr/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/codereadr/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Codereadr to Claude Code

### Connecting Codereadr to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

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

The Codereadr MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Codereadr account. It provides structured and secure access to your data collection and barcode scanning workflows, so your agent can create services, configure scan workflows, manage databases, and automate data collection processes for you.
- Automated service and workflow setup: Let your agent create new CodeREADr services and configure custom workflows for scanning, picking, delivery, and receiving tasks.
- Custom data collection form creation: Easily set up or modify data capture forms by adding or deleting custom questions after each scan.
- Real-time scan integration: Configure Direct Scan URLs, postback endpoints, or Google Sheets connectors to forward scan results instantly to your desired platforms.
- Device and database management: Direct your agent to delete devices or entire databases when they are no longer needed, streamlining your data environment.
- Kiosk and unattended scanning configuration: Enable and fine-tune Kiosk Mode for unattended or dedicated scanning stations to support high-volume operations.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `CODEREADR_COLLECT_DATA_WITH_QUESTIONS` | Collect Data With Questions | Create and attach custom questions to a CodeREADr service for data collection after scans. Use this to configure forms that collect additional information from users after each barcode scan. Requires a valid service ID from CODEREADR_RETRIEVE_SERVICES or CODEREADR_CREATE_SERVICE. |
| `CODEREADR_CONFIGURE_CONNECTOR` | Configure CodeREADr Connector | Helper to guide configuring the CodeREADr Connector for Google Sheets. There is no public API to programmatically create connector configurations. This tool validates your API connectivity (optional) and returns clear steps to proceed via the Google Sheets Add-on UI: https://www.codereadr.com/knowledgebase/codereadr-connector-add-on/ |
| `CODEREADR_CREATE_SERVICE` | Create CodeREADr Service | Creates a new CodeREADr service (barcode scanning workflow configuration). A service defines how barcode scans are processed - whether they're simply recorded, validated against a database, forwarded to an external URL, or display web content. Each validation_method type has different required parameters: 'database'/'ondevicedatabase' require database_id, 'postback' requires postback_url, 'webview' requires description (URL/HTML). |
| `CODEREADR_DELETE_DATABASE` | Delete CodeREADr Database | Delete a CodeREADr validation database by its ID. This permanently removes the database and all its barcode values. Use with caution. Note: A database cannot be deleted if it is currently linked to one or more services. You must unlink those services from the database first. Example: "Delete database with ID 1340798" |
| `CODEREADR_DELETE_DEVICE` | Delete Device | Tool to delete a device from CodeREADr. Uses the CodeREADr legacy API with section=devices and action=delete parameters. Note: Device deletion may have limited support in the CodeREADr API - only 'retrieve' and 'update' actions are officially documented for devices. |
| `CODEREADR_DELETE_QUESTION` | Delete Custom Question | Permanently deletes one or more custom questions from your CodeREADr account. Questions are used to collect additional data after scans. Once deleted, the question and all associated answer options are removed. This action cannot be undone. |
| `CODEREADR_DELETE_SERVICE` | Delete CodeREADr Service | Delete a CodeREADr service by its numeric ID. Use this to permanently remove a service/workflow configuration from your account. Note: This is a destructive action and cannot be undone. You can delete a single service, multiple services (comma-separated IDs), or all services. Example: "Delete service with ID 12345" |
| `CODEREADR_DELETE_USER` | Delete CodeREADr User | Deletes an existing user account from CodeREADr. Uses the CodeREADr legacy API endpoint (POST /api/ with section=users, action=delete). The user_id parameter can be a single ID, comma-separated list of IDs, or 'all'. Note: You cannot delete the account owner's app-user. The API will return an error if an invalid user_id is provided. |
| `CODEREADR_GENERATE_SCAN_LINK` | Generate Scan Link | Generates a CodeREADr scan link URI that opens the CodeREADr mobile app with a pre-filled scan value. Use this tool when you need to create clickable links that launch the CodeREADr scanner with a specific barcode, QR code, or identifier already entered. |
| `CODEREADR_LIST_SUPPORTED_BARCODE_TYPES` | List Supported Barcode Types | Lists barcode symbologies supported by CodeREADr for scanning. Returns 1D barcodes (Code 39, Code 128, EAN, UPC, Codabar, etc.), 2D barcodes (QR Code, Data Matrix, PDF-417, Aztec, etc.), and specialized formats. Use this to verify if a specific barcode type is supported before scanning. |
| `CODEREADR_RETRIEVE_DATABASES` | Retrieve CodeREADr Databases | Retrieves all validation databases configured in your CodeREADr account. Use this to list databases for barcode validation, see their IDs, names, item counts, and which services they're linked to. |
| `CODEREADR_RETRIEVE_DEVICES` | Retrieve Devices | Retrieve a list of devices registered to your CodeREADr account. This tool fetches information about devices linked to your account, including device IDs, UDIDs, names, and creation timestamps. Use this to monitor which devices have access to your CodeREADr services. |
| `CODEREADR_RETRIEVE_SCANS` | Retrieve Scan Records | Retrieve scan records from your CodeREADr account. Scans are the core data collected by CodeREADr when users scan barcodes using the mobile app. Each scan record includes the barcode value, timestamp, device info, validation status, and any collected responses. Use filters to narrow down results by service, user, device, date range, or status. Returns scan records in batches. Use limit and offset parameters for pagination. |
| `CODEREADR_RETRIEVE_SERVICES` | Retrieve CodeREADr Services | Retrieve configured services from your CodeREADr account. Services are the core organizational units in CodeREADr that define how barcode scans are validated and processed. Use this action to list all services or retrieve specific services by ID. |
| `CODEREADR_UPDATE_QUESTION` | Update CodeREADr Question | Add answer options to an existing CodeREADr question. Use this to add selectable answers for checkbox, dropdown, or option-type questions. The CodeREADr API does not support updating question text - to change text, delete and recreate the question. |
| `CODEREADR_UPDATE_SERVICE` | Update CodeREADr Service | Update an existing CodeREADr service configuration. Use this action to modify settings of a service by its ID. Only specified fields will be updated - omitted fields retain their current values. Common use cases: - Renaming a service - Changing postback/webhook URL - Enabling/disabling GPS tracking - Modifying duplicate scan handling - Setting time restrictions for service availability |

## Supported Triggers

None listed.

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

The Codereadr MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Codereadr account. It provides structured and secure access so Claude can perform Codereadr operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Codereadr account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["codereadr"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http codereadr-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['codereadr'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http codereadr-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Codereadr MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (codereadr-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http codereadr-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Codereadr MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your codereadr-composio entry in the list
- This confirms that Claude Code can now access Codereadr tools
If everything is wired up, you should see your codereadr-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Codereadr

The first time you try to use Codereadr tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Codereadr
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Codereadr authorization flow
- Return to the terminal and start using Codereadr through Claude Code
Once authenticated, you can ask Claude Code to perform Codereadr operations in natural language. For example:
- "Create a new barcode scanning service"
- "Configure survey questions after each scan"
- "Enable Kiosk Mode for unattended device"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["codereadr"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http codereadr-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['codereadr'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http codereadr-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Codereadr with Claude Code using Composio's MCP server. Now you can interact with Codereadr directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Codereadr operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Codereadr operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Codereadr MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/codereadr/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/codereadr/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/codereadr/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/codereadr/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/codereadr/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/codereadr/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/codereadr/framework/cli)
- [Google ADK](https://composio.dev/toolkits/codereadr/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/codereadr/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/codereadr/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/codereadr/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/codereadr/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/codereadr/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Codereadr MCP?

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

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

Yes, you can. Claude Code 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 Codereadr tools.

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

Yes, absolutely. You can configure which Codereadr 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 Codereadr data and credentials are handled as safely as possible.

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