xyte-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XYTE_HUB_URL | No | Override the hub base URL | https://hub.xyte.io |
| XYTE_ENTRY_URL | No | Override the entry base URL | |
| XYTE_ORG_API_KEY | No | Organization-scoped API key. Either this or XYTE_PARTNER_API_KEY must be set. | |
| XYTE_MCP_READ_ONLY | No | Set to '1' to refuse all mutating endpoints. Writes are permitted by default. | |
| XYTE_MCP_TIMEOUT_MS | No | Per-request timeout in milliseconds | 15000 |
| XYTE_PARTNER_API_KEY | No | Partner-scoped API key. Either this or XYTE_ORG_API_KEY must be set. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xyte_endpoints_listA | Discover Xyte platform API endpoints. Returns compact rows; call xyte_endpoint_describe for a specific endpoint's parameters before calling it. Filter with namespace/group/method/search to keep results small. |
| xyte_endpoint_describeA | Show the full contract for one endpoint: required path parameters, accepted query parameters, body shape and which credential it needs. Call this before xyte_api_call when you are unsure of an endpoint's arguments. |
| xyte_api_callA | Invoke a Xyte platform API endpoint by key. Use xyte_endpoint_describe first if you are unsure of the parameters. Mutating endpoints run unless the server was started read-only; DELETE additionally requires confirm. |
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 3 tools
Each tool has a distinct role: listing endpoints, describing a specific endpoint, and making an API call. There is no overlap or ambiguity.
All tools start with 'xyte_' and follow a resource_action pattern, but there is a minor inconsistency: 'xyte_endpoints_list' uses plural 'endpoints' while 'xyte_endpoint_describe' uses singular 'endpoint'.
With three tools, the server covers the essential workflow for an API wrapper: discover, describe, and call. It is well-scoped and not excessive or sparse.
The tools provide a complete cycle for interacting with the Xyte API: listing available endpoints, getting detailed parameters for a specific endpoint, and executing the call. No obvious gaps are present.