AxonHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AXONHUB_URL | Yes | The base URL of your AxonHub instance, e.g., https://ai.neo7.cn | |
| AXONHUB_TOKEN | Yes | Your AxonHub admin login token for Bearer authentication | |
| AXONHUB_PROJECT_ID | No | Optional default project ID |
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 |
|---|---|
| axonhub_statusC | Get request totals, latency, token totals, and channel success rates from the AxonHub dashboard. |
| axonhub_list_projectsB | List AxonHub projects with status and pagination information. |
| axonhub_list_channelsA | List channels and their health, quota, model, and limiter status. Credentials are never returned. |
| axonhub_list_modelsA | List configured models, capabilities, costs, limits, and associated channel counts. |
| axonhub_list_requestsA | List recent requests with status, latency, executions, token usage, and cost. Request/response payloads are excluded. |
| axonhub_usageA | Get token and cost usage grouped by channel, model, API key, or user. |
| axonhub_schemaB | Inspect one GraphQL type so an AI client can adapt to the installed AxonHub version. |
| axonhub_graphql_queryA | Run a custom query against /admin/graphql. Mutations and subscriptions are rejected; sensitive fields are redacted. |
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: status, listing projects/channels/models/requests, schema inspection, usage analytics, and a generic query. No overlap or ambiguity.
All tools follow the 'axonhub_verb_noun' pattern (e.g., list_projects, get_status, run_query). Consistent and predictable.
8 tools cover the core monitoring and admin operations without redundancy. The count is well-scoped for the domain.
The surface covers status, listing, schema introspection, usage, and a flexible query escape hatch. It lacks per-entity detail getters, but for an admin/metrics gateway this is sufficient.