How to integrate Openlayer MCP with Claude Code

Manage your Openlayer 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 - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Openlayer logoOpenlayer
Api Key

Openlayer is an AI quality platform for managing projects, monitoring production data, evaluating tests, and inspecting model performance. Use it to catch regressions, track production quality, and keep AI applications reliable before and after release.

10 Tools

Introduction

Manage your Openlayer 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:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Openlayer with

Why use Composio?

  • 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.

Connecting Openlayer to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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

The Openlayer MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Openlayer account. It provides structured and secure access to your projects, versions, monitoring data sources, tests, results, and workspace details, so your agent can review projects, inspect model versions, check monitoring status, analyze test outcomes, and track workspace usage on your behalf.

  • Project and version reviews: Have your agent list Openlayer projects, inspect their versions, and compare processing status and passing, failing, and total test counts.
  • Production monitoring checks: Let the agent find monitoring data sources and review their backend, monitoring status, record counts, and test counts.
  • Test configuration discovery: Direct your agent to list tests for a project and narrow them by category, archive state, origin, production data use, or suggested status.
  • Test result analysis: Instruct your agent to review results for project versions, monitoring data sources, or individual tests, including execution status and available generated insights.
  • Workspace usage visibility: Have your agent check workspace status, connected account membership, usage counts, and current plan limits.

Connecting Openlayer via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Openlayer) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

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

Install Claude Code

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

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

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
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

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

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

Create a script to generate a Composio MCP URL for Openlayer. This URL will be used to connect Claude Code to Openlayer.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Openlayer
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

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

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Openlayer MCP to Claude Code

bash
claude mcp add --transport http openlayer-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

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 (openlayer-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.

9

Verify the installation

bash
claude mcp list

Check that your Openlayer MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your openlayer-composio entry in the list
  • This confirms that Claude Code can now access Openlayer tools

If everything is wired up, you should see your openlayer-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Openlayer

The first time you try to use Openlayer tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Openlayer
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Openlayer authorization flow
  • Return to the terminal and start using Openlayer through Claude Code

Once authenticated, you can ask Claude Code to perform Openlayer operations in natural language. For example:

  • "List failing Openlayer tests for deployment"
  • "Summarize production drift in Openlayer project"
  • "Create Openlayer report for model performance"

Complete Code

Here's the complete code to get you started with Openlayer and Claude Code:

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

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

Conclusion

You've successfully integrated Openlayer with Claude Code using Composio's MCP server. Now you can interact with Openlayer directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Openlayer 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 Openlayer 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.

TOOLS

Supported Tools

Every Openlayer action and event your agent gets out of the box.

Get Data Source

Return one Openlayer monitoring data source, including its backend, monitoring status, record and test counts, and optional project or workspace details.

Get Project Version

Return one Openlayer project commit or version with its processing status, commit metadata, storage URI, and passing, failing, and total test counts.

Get Workspace

Return a workspace's identity, status, connected-account membership, usage counts, and plan limits.

List Data Sources

Return one page of monitoring data sources for an Openlayer project, optionally filtered by name.

List Data Source Test Results

Return one page of the latest monitoring test results for an Openlayer data source, optionally filtered by test category or execution status.

List Projects

Return one page of projects visible to the connected Openlayer workspace, optionally filtered by name or task type.

List Project Versions

Return one page of commits and versions for an Openlayer project, including processing status, commit metadata, and passing, failing, and total test counts.

List Project Version Test Results

Return one page of test results for a project version, optionally filtered by test category, archive state, or result status.

List Test Results

Return one page of results for a test, with optional project-version, data-source, and status filters and optional generated insights.

List Tests

Return one page of tests configured for an Openlayer project, with filters for category, archive state, origin version, production-data use, and suggested status.

FAQ

Frequently asked questions

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

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 Openlayer tools.

Yes, absolutely. You can configure which Openlayer 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.

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 Openlayer data and credentials are handled as safely as possible.

Start with Openlayer.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Openlayer tool your agent needs.Free to start.

Start building