ExisOne MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXISONE_API_URL | Yes | API URL (must be HTTPS). Default: https://www.exisone.com | |
| EXISONE_TIMEOUT | No | Request timeout in ms (default: 30000) | |
| EXISONE_TENANT_ID | Yes | Your tenant identifier | |
| EXISONE_ACCESS_TOKEN | Yes | Your API token in format exo_at_{publicId}_{secret} |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List all products for the current tenant. Returns product details including name, price, trial days, and license duration. |
| list_licensesA | List all licenses, optionally filtered by product. Returns license keys, customer emails, activation status, and expiration dates. |
| generate_licenseA | Generate a new activation key for a product. The license key will be created and can be sent to the customer. |
| get_licenseA | Get detailed information about a specific license by its activation key, including activation history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.