XO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCESS_TOKEN | Yes | Your XO platform access token | |
| DEPLOYMENT_ID | Yes | Unique deployment identifier from XO Launchpad |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_to_xoD | Deploy to XO |
| start_xo_appB | Start the XO app |
| stop_xo_appB | Stop the XO app |
| remove_xo_appA | Remove the XO app |
| get_xo_app_logsC | Get the XO app logs |
| expose_xo_appB | Expose the XO app to the domain name by calling the /expose-xo-app endpoint |
| update_knowledgebase_using_textC | Update knowledgebase using text content |
| ask_questionD | Ask a question to the knowledge base |
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 8 tools
Each tool has a clear, distinct purpose: two for knowledge base operations and six for app lifecycle management. No overlapping functionality.
Most tools follow a verb_noun pattern (e.g., start_xo_app, remove_xo_app), but 'deploy_to_xo' and 'update_knowledgebase_using_text' deviate slightly in structure, causing minor inconsistency.
With 8 tools, the set is well-scoped for managing XO apps and a knowledge base—neither too few nor too many for the domain.
The app lifecycle is well-covered (deploy, start, stop, remove, logs, expose), but the knowledge base is limited to ask and update via text, missing delete or query options, which is a minor gap.