astrovisor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASTROVISOR_URL | No | API base URL. | https://astrovisor.io |
| INTERNAL_MCP_URL | No | Internal adapter URL. | http://127.0.0.1:3001/mcp |
| ASTROVISOR_API_KEY | Yes | Your AstroVisor dashboard API key starting with 'pk-'. | |
| ASTROVISOR_TOOL_MODE | No | Either 'compact' or 'full'. | compact |
| MCP_PUBLIC_HTTP_HOST | No | Gateway bind host. | 127.0.0.1 |
| MCP_PUBLIC_HTTP_PORT | No | Gateway bind port. | 3002 |
| ASTROVISOR_OPENAPI_URL | No | OpenAPI document URL override. | https://astrovisor.io/openapi.json |
| API_KEY_VALIDATION_PATH | No | Non-billable key validation endpoint. | /internal/mcp/validate-api-key |
| ASTROVISOR_RESPONSE_VIEW | No | Default response view. | compact |
| ASTROVISOR_RESULT_TTL_MS | No | Result cache TTL in milliseconds. | 1800000 |
| API_KEY_VALIDATION_CACHE_MS | No | Validation cache time in milliseconds. | 60000 |
| ASTROVISOR_RESULT_MAX_ENTRIES | No | Maximum number of cached results. | 128 |
| MCP_INTERNAL_VALIDATION_TOKEN | No | Internal validation credential (required for public gateway). | |
| ASTROVISOR_DEFAULT_TOKEN_BUDGET | No | Serialized byte budget. | implementation default |
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 |
|---|---|
| astrovisor_requestB | Call any AstroVisor API operation by operationId. Supports compact serialization and follow-up retrieval by resultId. |
| astrovisor_openapi_searchA | Search AstroVisor OpenAPI operations by text (operationId/summary/path/tag). Returns top matches. |
| astrovisor_openapi_listA | List OpenAPI operations with pagination and optional filters. |
| astrovisor_openapi_getB | Get OpenAPI metadata for a specific operationId (method/path/params/requestBody). |
| astrovisor_result_getB | Get stored full result by resultId with optional selective serialization. |
| astrovisor_conventionsA | Get MCP interoperability conventions and parameter profiles for LLM clients. |
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 6 tools
Each tool has a distinct purpose: one for executing API calls, three for exploring OpenAPI specs, one for retrieving results, and one for conventions. No overlapping functionality.
All tool names follow a consistent 'astrovisor_<action>' pattern using snake_case, making them predictable and easy to understand.
With 6 tools, the server is well-scoped for its purpose of interacting with an API explorer and executor. Neither too few nor too many.
The tool set covers the core workflow: exploring operations, retrieving metadata, executing requests, and fetching results. A minor gap is the lack of a way to list stored results, but this is acceptable given the design.