# How to integrate Gagelist MCP with Claude Code

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

## Introduction

Manage your Gagelist 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 Gagelist with

- [OpenAI Agents SDK](https://composio.dev/toolkits/gagelist/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/gagelist/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/gagelist/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/gagelist/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/gagelist/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/gagelist/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/gagelist/framework/cli)
- [Google ADK](https://composio.dev/toolkits/gagelist/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/gagelist/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/gagelist/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/gagelist/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/gagelist/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/gagelist/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 Gagelist to Claude Code

### Connecting Gagelist 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 Gagelist MCP server, and what's possible with it?

The Gagelist MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Gagelist account. It provides structured and secure access to your calibration records and asset management workflows, so your agent can perform actions like adding new gages, managing calibration events, generating certificates, and retrieving account information on your behalf.
- Seamless calibration record management: Direct your agent to add, update, or delete calibration records, keeping your asset compliance up-to-date with minimal manual effort.
- Automated gage and manufacturer tracking: Have the agent add new gages or manufacturers to your Gagelist inventory, or remove outdated entries as your equipment changes.
- Instant calibration certificate generation: Let your agent generate official PDF calibration certificates from existing records, streamlining audit and reporting processes.
- Account insights and status checks: Quickly retrieve your account settings or overall status, giving you a real-time view into your calibration program's health.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `GAGELIST_ADD_CALIBRATION_RECORD` | Add Calibration Record | Creates a new calibration record in GageList to document equipment calibration results. Use this tool to record calibration activities including test results, dates, technician info, and equipment condition. Can optionally link to an existing gage record via EquipmentRefId, or create a standalone calibration record. Supports detailed test data, attachments, and custom fields. |
| `GAGELIST_ADD_GAGE_RECORD` | Add Gage Record | Tool to add a new gage record. Use after gathering all required gage attributes to create a record. |
| `GAGELIST_ADD_MANUFACTURER` | Add Manufacturer | Creates a new manufacturer record in the GageList calibration management system. A manufacturer represents the company that produces gages and measurement instruments. Use this action when you need to add a new manufacturer to the system for tracking and managing calibration records for their equipment. Returns the unique identifier of the newly created manufacturer record. |
| `GAGELIST_AUTHENTICATE_WITH_GAGELIST` | Authenticate with Gagelist | Tool to obtain a Gagelist API access token. Use when you need to authenticate with Gagelist using client credentials. Returns OAuth2 tokens for subsequent requests. |
| `GAGELIST_DELETE_CALIBRATION_RECORD` | Delete Calibration Record | Deletes a calibration record by its ID. This is a destructive operation that permanently removes the record. Verify the record exists before deletion. |
| `GAGELIST_DELETE_GAGE_RECORD` | Delete Gage Record | Deletes a gage record by its ID. The record must exist in the system to be deleted successfully. This operation is destructive and cannot be undone. |
| `GAGELIST_DELETE_MANUFACTURER` | Delete Manufacturer | Tool to delete a manufacturer by its ID. Use after confirming the manufacturer exists. |
| `GAGELIST_GENERATE_CALIBRATION_CERTIFICATE` | Generate Calibration Certificate | Tool to generate a PDF certificate from a calibration record. Use after ensuring record ID and authentication. |
| `GAGELIST_GET_ACCOUNT_SETTINGS` | Get Account Settings | Tool to get account settings. Use after successful authentication to retrieve user-specific settings. |
| `GAGELIST_GET_ACCOUNT_STATUS` | Get account status | Tool to retrieve account status. Use after authenticating with Gagelist. |
| `GAGELIST_GET_ALL_CALIBRATION_RECORDS` | Get all calibration records | Tool to retrieve a paginated list of calibration records. Use after obtaining a valid access token. |
| `GAGELIST_GET_ALL_GAGE_RECORDS` | Get All Gage Records | Tool to retrieve a paginated list of gage records. Use after confirming the access token. |
| `GAGELIST_GET_ALL_MANUFACTURERS` | Get All Manufacturers | Tool to retrieve a list of all manufacturers. Use after obtaining a valid access token. Returns manufacturer details including ID, name, contact information, and timestamps. |
| `GAGELIST_GET_ATTACHMENT` | Get Attachment | Tool to retrieve an attachment by its ID. Use when you need to download file attachments from the system. |
| `GAGELIST_GET_CUSTOM_FIELDS` | Get Custom Fields | Tool to retrieve custom field definitions. Use when you need to list all custom fields configured for both gage and calibration items after authentication. |
| `GAGELIST_GET_SINGLE_CALIBRATION_RECORD` | Get Single Calibration Record | Tool to retrieve details of a single calibration record. Use when you need a specific record's detailed data. Ensure a valid Bearer token is set. |
| `GAGELIST_GET_SINGLE_GAGE_RECORD` | Get Single Gage Record | Retrieves comprehensive details of a single gage/gauge record from GageList by its unique ID. Returns complete gage information including: serial number, control number, manufacturer details, calibration dates and intervals, measurement specifications (range, tolerance, unit of measure), location, responsible user, test templates, and attached files. Use this after obtaining a valid gage ID from GAGELIST_GET_ALL_GAGE_RECORDS or GAGELIST_ADD_GAGE_RECORD. Example: GetSingleGageRecord(id=123) |
| `GAGELIST_UPDATE_ACCOUNT_SETTINGS` | Update Account Settings | Tool to update account settings. Use after retrieving current settings to apply user preference changes. |
| `GAGELIST_UPDATE_CUSTOM_FIELD_VALUES` | Update Custom Field Values | Tool to update custom field values. Use when you need to set or modify custom field values for a gage or calibration record after authentication. |
| `GAGELIST_UPDATE_MANUFACTURER` | Update Manufacturer | Tool to update a manufacturer by its ID. Use after confirming the manufacturer exists. |
| `GAGELIST_UPLOAD_ATTACHMENT_TO_GAGE_RECORD` | Upload Attachment To Gage Record | Tool to upload an attachment to a gage record. Use when adding files to an existing gage record. |

## Supported Triggers

None listed.

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

The Gagelist 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 Gagelist account. It provides structured and secure access so Claude can perform Gagelist 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 Gagelist 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=["gagelist"],
)

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 gagelist-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: ['gagelist'],
});

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 gagelist-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 Gagelist 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 (gagelist-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 gagelist-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 Gagelist MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your gagelist-composio entry in the list
- This confirms that Claude Code can now access Gagelist tools
If everything is wired up, you should see your gagelist-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Gagelist

The first time you try to use Gagelist tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Gagelist
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Gagelist authorization flow
- Return to the terminal and start using Gagelist through Claude Code
Once authenticated, you can ask Claude Code to perform Gagelist operations in natural language. For example:
- "Add a new calibration record for this gage"
- "Generate calibration certificate for equipment ID 2345"
- "List all gages due for calibration this month"

## 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=["gagelist"],
)

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 gagelist-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: ['gagelist'],
});

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 gagelist-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Gagelist with Claude Code using Composio's MCP server. Now you can interact with Gagelist directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Gagelist 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 Gagelist 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 Gagelist MCP Agent with another framework

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

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [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.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement.

## Frequently Asked Questions

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

With a standalone Gagelist MCP server, the agents and LLMs can only access a fixed set of Gagelist tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Gagelist 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 Gagelist tools.

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

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

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