Aspro Cloud MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASPRO_API_KEY | Yes | API key from Aspro Cloud settings | |
| ASPRO_COMPANY | Yes | Your company subdomain (e.g., 'mycompany') |
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 |
|---|---|
| list_leadsA | List CRM deals (leads) with optional filters |
| get_leadA | Get a CRM deal (lead) by ID |
| create_leadB | Create a new CRM deal (lead) |
| update_leadB | Update an existing CRM deal (lead) |
| delete_leadB | Delete a CRM deal (lead) by ID |
| list_pipelinesA | List all CRM sales pipelines |
| list_pipeline_stagesA | List pipeline stages, optionally filtered by pipeline |
| list_tasksA | List tasks with optional filters. By default returns only NON-ARCHIVED tasks (archive_status=0). "Active tasks" and "tasks" always means non-archived. To get archived tasks, pass archive_status=10. Status values (use 'status' param): 1 = New (created but not started — most tasks accumulate here as backlog) 3 = In Progress (actively being worked on right now) 4 = Waiting Review (done by assignee, pending verification) 5 = Done (completed but not yet archived) To find tasks truly in progress use status=3. To find all incomplete tasks use status=1, 3, or 4. Type values: 0=Task, 1=Inbox, 20=Event, 30=Template |
| get_taskA | Get a task by ID |
| create_taskC | Create a new task |
| update_taskB | Update an existing task |
| delete_taskB | Delete a task by ID |
| list_workflowsB | List all task workflows |
| list_workflow_stagesB | List workflow stages, optionally filtered by workflow |
| search_usersA | Search users by name or email. Returns id, name and username (email) — use id as responsible_id for tasks or assignee_id for deals |
| get_userB | Get detailed information about a user by ID |
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 16 tools
Tools cleanly separate into leads, tasks, workflow/pipeline configuration, and users. Each tool targets a unique resource-action pair, such as list_pipelines versus list_pipeline_stages, so there is no real ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (list_*, get_*, create_*, update_*, delete_*, search_*). This makes the toolset predictable and easy to navigate.
At 16 tools, the server is slightly above the ideal 3-15 range but still well-scoped. The count is justified by covering two major domains (leads and tasks) plus user lookup, with minimal redundancy.
Both leads and tasks have full CRUD coverage, complemented by pipeline/stage and workflow/stage listing. Minor gaps exist, such as no user listing (only search) and no CRUD for pipelines/workflows, but these are typically configuration-level and do not block core workflows.