How to integrate Devolens / Cryptolens MCP with Claude Code

Manage your Devolens / Cryptolens 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

Devolens / Cryptolens logoDevolens / Cryptolens
Api Key

Devolens provides the Cryptolens API for software licensing, license keys, products, customers, entitlements, and usage analytics. Use it to automate license lifecycle management and protect paid software without building a licensing backend.

10 Tools

Introduction

Manage your Devolens / Cryptolens 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 Devolens / Cryptolens 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 Devolens / Cryptolens 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 Devolens / Cryptolens MCP server, and what's possible with it?

The Devolens / Cryptolens MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Devolens / Cryptolens account. It provides structured and secure access to your software licensing data, so your agent can inspect license keys, review products and templates, find customers and resellers, analyze daily usage, and investigate account activity on your behalf.

  • License key lookup and search: Have your agent retrieve a specific license key with its activation details, or search the keys associated with a product.
  • Product and template review: Let the agent list the products and license templates available in your Cryptolens account.
  • Customer and partner discovery: Direct your agent to find customers, registered license users, and resellers connected to your account.
  • Daily usage analysis: Instruct your agent to review daily usage totals for a product across a selected date range.
  • Activity and message investigation: Have your agent inspect account messages and review web request logs by product, license key, machine, event, or time period.

Connecting Devolens / Cryptolens 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 Devolens / Cryptolens) 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 Devolens / Cryptolens 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: ['devolens'],
});

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

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

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 Devolens / Cryptolens
  • 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 Devolens / Cryptolens MCP to Claude Code

bash
claude mcp add --transport http devolens-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 (devolens-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 Devolens / Cryptolens MCP server is properly configured.

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

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

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Devolens / Cryptolens

The first time you try to use Devolens / Cryptolens tools, you'll be prompted to authenticate.

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

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

  • "List expired Cryptolens license keys"
  • "Create license key for enterprise customer"
  • "Show usage analytics for active products"

Complete Code

Here's the complete code to get you started with Devolens / Cryptolens 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: ['devolens'],
});

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

Conclusion

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

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Devolens / Cryptolens 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 Devolens / Cryptolens 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 Devolens / Cryptolens action and event your agent gets out of the box.

Get License Key

Retrieve one license key and optional activation metadata by its product ID and key string.

List Customers

Search or list customers visible to the connected Cryptolens account, including reseller-visible customer groups returned by the API.

List Daily Usage Aggregates

Return one page of daily Cryptolens usage aggregates, optionally filtered by product and inclusive date range.

List License Keys

List and search one page of license keys for a Cryptolens product.

List License Templates

Return the license templates available to the connected Cryptolens account.

List License Users

Return registered Cryptolens license users, optionally limited to one customer.

List Messages

Return Cryptolens account messages, optionally filtered by channel or creation time.

List Products

Return the Cryptolens products visible to the connected access token.

List Resellers

Search or list resellers visible to the connected Cryptolens account.

List Web API Logs

Inspect one page of Cryptolens Web API request logs with optional product, license-key, machine, event, and time filters.

FAQ

Frequently asked questions

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

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

Start with Devolens / Cryptolens.It takes 30 seconds.

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

Start building