aspro-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASPRO_API_KEY | Yes | Your API key for Aspro.Cloud, passed as ?api_key=... on every request | |
| ASPRO_COMPANY | Yes | The subdomain part of the Aspro.Cloud URL, e.g., your_company from https://your_company.aspro.cloud | |
| ASPRO_BASE_URL | No | Optional full base URL to override the one built from ASPRO_COMPANY | |
| ASPRO_TIMEOUT_MS | No | Optional timeout in milliseconds for requests, default 30000 |
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 |
|---|---|
| aspro_list_modulesA | List all top-level Aspro.Cloud API modules (crm, fin, agile, task, etc.) with entity and operation counts. |
| aspro_list_entitiesA | List entities inside a given module along with the methods available on each entity. |
| aspro_list_methodsA | List operations (HTTP method + path + short description) for a given module and optional entity. |
| aspro_searchA | Search operations by keyword across module/entity/method/path/description/tags. Handles Russian inflection and multi-word queries ('создать задачу', 'сделки'). |
| aspro_describeA | Return the full schema for one operation: HTTP method, path, whether it mutates data, request-body fields and the fields present in the response. |
| aspro_callA | Read data from Aspro.Cloud — the |
| aspro_writeA | Create, update or DELETE data in Aspro.Cloud. Destructive — the change is applied to the live account and cannot be undone from here. Run aspro_describe first. Pass the entity id via |
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 clearly distinct role: discovery (modules, entities, methods), search, schema description, read execution, and write execution. There is no overlap in purpose, so an agent can easily select the right tool for each step.
All tool names follow the aspro_ prefix with a descriptive verb: aspro_list_modules, aspro_list_entities, aspro_list_methods, aspro_search, aspro_describe, aspro_call, aspro_write. The pattern is consistent and predictable, making it easy to infer functionality from the name.
Seven tools is well-scoped for an API exploration and interaction server. Each tool earns its place, covering the full workflow from discovery to execution without unnecessary redundancy or bloat.
The tool surface covers the complete API interaction lifecycle: exploring modules and entities, listing methods, searching, describing schemas, reading data, and writing data. No obvious gaps are apparent for the stated purpose of working with Aspro.Cloud.