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') |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kazan-project-manufactory/aspo-cloud-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server