ExisOne MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ExisOne MCP Server Generate a license for jane@example.com for MyProduct Pro"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ExisOne MCP Server
An MCP (Model Context Protocol) server that enables AI assistants like Claude to manage software licenses through natural language commands.
What is This?
This MCP server connects Claude Desktop to the ExisOne software licensing platform. Once configured, you can manage licenses using natural language:
"List all my products" - View your product catalog
"Show me all licenses" - List all license keys
"Generate a license for customer@email.com for MyProduct" - Create new keys
"Get details for license XXXX-XXXX-XXXX-XXXX" - View specific license info
No more clicking through dashboards - just ask Claude.
Related MCP server: ELM MCP
Quick Start
1. Clone and Build
git clone https://github.com/exisllc/exisone-mcp.git
cd exisone-mcp
npm install
npm run build2. Get Your Access Token
Log in to ExisOne
Go to Access Tokens in the sidebar
Click Create Token
Name it "MCP Server" and select permissions:
generate,verifyCopy the token (format:
exo_at_xxx_yyy) - shown only once!
3. Configure Claude Desktop
Edit your Claude Desktop config file:
Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows example:
{
"mcpServers": {
"exisone": {
"command": "node",
"args": ["C:\\Users\\YOURNAME\\exisone-mcp\\dist\\index.js"],
"env": {
"EXISONE_API_URL": "https://www.exisone.com",
"EXISONE_ACCESS_TOKEN": "exo_at_YOUR_PUBLIC_ID_YOUR_SECRET",
"EXISONE_TENANT_ID": "1"
}
}
}
}macOS/Linux example:
{
"mcpServers": {
"exisone": {
"command": "node",
"args": ["/Users/yourname/exisone-mcp/dist/index.js"],
"env": {
"EXISONE_API_URL": "https://www.exisone.com",
"EXISONE_ACCESS_TOKEN": "exo_at_YOUR_PUBLIC_ID_YOUR_SECRET",
"EXISONE_TENANT_ID": "1"
}
}
}
}Replace:
The path with the actual path where you cloned the repo (use
\\for Windows,/for macOS/Linux)EXISONE_ACCESS_TOKENwith your actual tokenEXISONE_TENANT_IDwith your tenant ID (visible in dashboard settings)
4. Restart Claude Desktop
Important: You must fully quit Claude Desktop - closing the window is not enough as it continues running in the background.
Windows: Right-click the Claude icon in the system tray → Quit, or use Task Manager to end the "Claude" process
macOS: Right-click the dock icon → Quit, or use Cmd+Q
Reopen Claude Desktop and go to Settings → Developer to verify the ExisOne server appears in the list.
Available Tools
Tool | Description | Parameters |
| List all products for your tenant | None |
| List licenses with optional filters |
|
| Generate a new activation key |
|
| Get detailed license information |
|
Example Conversations
List products:
"What products do I have in ExisOne?"
Generate a license:
"Create a 30-day license for john@example.com for MyApp Pro"
Check a license:
"Show me the details for license ABCD-1234-EFGH-5678"
Filter licenses:
"List all active licenses for MyApp"
Configuration Options
Environment Variable | Required | Description |
| Yes | API URL (must be HTTPS). Default: |
| Yes | Your API token in format |
| Yes | Your tenant identifier |
| No | Request timeout in ms (default: 30000) |
Security Notes
Token Security: Store your access token securely. Never commit it to version control.
HTTPS Required: The MCP server validates that the API URL uses HTTPS.
Permission Scope: The server inherits permissions from your access token. Only grant needed permissions.
Tenant Isolation: Each token is scoped to a specific tenant.
Troubleshooting
Config changes not taking effect (Most Common Issue!)
Claude Desktop runs in the background even after closing the window. You must fully quit it:
Windows: Open Task Manager (Ctrl+Shift+Esc), find "Claude" and click "End Task"
Alternative: Right-click the Claude icon in the system tray (bottom-right corner) → Quit
Then reopen Claude Desktop
Claude doesn't show ExisOne tools
Go to Settings → Developer to check if the server is listed
Verify your config file path is correct for your OS
Check that the path to
dist/index.jsis absolute and correctMake sure Claude Desktop is fully quit (not running in background) before restarting
Check Claude Desktop logs for error messages
"EXISONE_API_URL environment variable is required"
Make sure all three environment variables are set in your Claude config:
EXISONE_API_URLEXISONE_ACCESS_TOKENEXISONE_TENANT_ID
"API error 401" or "API error 403"
Verify your access token is correct and not expired
Check that the token has the required permissions (
generate,verify)Ensure the tenant ID matches your account
Development
# Install dependencies
npm install
# Build TypeScript
npm run build
# Watch mode for development
npm run dev
# Type check without building
npm run typecheckProject Structure
exisone-mcp/
├── src/
│ ├── index.ts # Entry point with stdio transport
│ ├── server.ts # MCP server setup
│ ├── config.ts # Environment configuration
│ ├── api/
│ │ ├── client.ts # HTTP client for ExisOne API
│ │ └── types.ts # TypeScript interfaces
│ └── tools/
│ ├── index.ts # Tool registry
│ ├── list-products.ts
│ ├── list-licenses.ts
│ ├── generate-license.ts
│ └── get-license.ts
├── dist/ # Compiled JavaScript
├── package.json
├── tsconfig.json
└── README.mdAdding New Tools
Create a new file in
src/tools/(e.g.,deactivate-license.ts)Define the tool schema with name, description, and inputSchema
Implement the handler function
Register in
src/tools/index.ts
Example:
export const myTool = {
name: "my_tool",
description: "What the tool does",
inputSchema: {
type: "object" as const,
properties: {
param1: { type: "string", description: "..." }
},
required: ["param1"]
}
};
export async function handleMyTool(args, client) {
// Implementation
return { content: [{ type: "text", text: "Result" }] };
}Links
License
MIT License - see LICENSE file for details.
Support
Available Tools
4 toolsgenerate_licenseA
Generate a new activation key for a product. The license key will be created and can be sent to the customer.
Inputs: email (required), productName (required), planId, validityDays.
get_licenseA
Get detailed information about a specific license by its activation key, including activation history.
Inputs: activationKey (required).
list_licensesA
List all licenses, optionally filtered by product. Returns license keys, customer emails, activation status, and expiration dates.
Inputs: productId, activeOnly, productName.
list_productsA
List all products for the current tenant. Returns product details including name, price, trial days, and license duration.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a clearly distinct action and resource: listing products, listing licenses, generating a new license, and fetching a single license by key. There is no meaningful overlap or ambiguity among the four tools.
All tool names follow a consistent verb_noun pattern in snake_case, such as list_products, list_licenses, generate_license, and get_license. The naming is predictable and easy for an agent to pattern-match.
Four tools is well-scoped for a focused license management server. Each tool represents a core operation, and the set does not feel padded or unnecessarily large.
The set covers listing products, listing licenses, generating licenses, and retrieving license details, which handles the primary issuance and lookup workflow. However, there are no update, revoke, or deactivation operations for licenses, leaving a notable lifecycle gap.
Maintenance
Related MCP Connectors
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Connect AI assistants to Subotiz - Using Subotiz's external capabilities through natural language
Connect AI assistants to Subotiz - Using Subotiz's external capabilities through natural language
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely perform actions on your computer including file system management, command execution, clipboard access, application launching, and local search with license-based monetization built in.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with IBM Engineering Lifecycle Management (ELM), including DOORS Next Generation, EWM, and ETM, for managing requirements, work items, tests, and project builds through natural language.MIT

Public Gateway MCPofficial
AlicenseCqualityCmaintenanceConnects AI assistants to Axcient for real-time data retrieval and actions through natural conversation.3Apache 2.0- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control supported CAD applications through natural-language or direct tool calls for drawing, layer, block, entity, file, and data-export operations.-