XAPIHub MCP Extension
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Optional debug logging configuration (e.g., xapihub:*) | |
| XAPIHUB_TOKEN | Yes | Your XAPIHub bearer token | |
| XAPIHUB_BASE_URL | Yes | The base URL for the XAPIHub API (e.g., https://api-dev.xapihub.io) | https://api-dev.xapihub.io |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userB | Get current user details from XAPIHub API |
| test_xapihub_connectionB | Test connection to XAPIHub API |
| get_accessed_organizationsB | Get recent accessed organizations from XAPIHub API |
| get_recent_accessed_projectsC | Get recent accessed projects for a specific organization from XAPIHub API |
| search_projectsC | Search for projects in an organization with comprehensive filtering and pagination options |
| get_cataloguesC | Get catalogues for a specific organization and project from XAPIHub API |
| get_api_detailsC | Get API details for a specific catalogue collection using filter endpoint from XAPIHub API |
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 7 tools
Each tool has a distinct and clearly defined purpose targeting different resources or actions within the XAPIHub domain. For example, get_accessed_organizations retrieves organizations, get_api_details fetches API specifics, and get_catalogues handles catalogues, with no overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_accessed_organizations, get_api_details, and search_projects. This uniformity makes the tool set predictable and easy to understand.
With 7 tools, the server is well-scoped for its purpose of interacting with XAPIHub API resources like organizations, projects, catalogues, and users. Each tool serves a specific function without redundancy, fitting within the typical 3-15 tool range.
The tool set covers core read operations for organizations, projects, catalogues, users, and API details, including search and connection testing. A minor gap exists in write operations (e.g., create or update resources), but agents can still perform essential queries and validations effectively.