Autotask MCP Server
by ddurko1950
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node.js environment | development |
| AUTH_MODE | No | Authentication mode: 'env' for local credentials, 'gateway' for hosted gateway mode where credentials are injected via HTTP headers. | env |
| LOG_LEVEL | No | Logging level: error, warn, info, debug | info |
| LOG_FORMAT | No | Log output format: simple or json | simple |
| MCP_HTTP_HOST | No | HTTP transport bind address | 0.0.0.0 |
| MCP_HTTP_PORT | No | HTTP transport port (only used when MCP_TRANSPORT=http) | 8080 |
| MCP_TRANSPORT | No | Transport type: 'stdio' for local/desktop, 'http' for remote/Docker deployments. | stdio |
| AUTOTASK_SECRET | No | Autotask API secret key | |
| MCP_SERVER_NAME | No | MCP server name | autotask-mcp |
| AUTOTASK_API_URL | No | Override Autotask API endpoint URL. If not set, it is auto-detected from the username via Autotask's zoneInformation endpoint. | |
| AUTOTASK_USERNAME | No | Autotask API username (email) | |
| AUTOTASK_INTEGRATION_CODE | No | Autotask integration code | |
| AUTOTASK_ENHANCE_CONCURRENCY | No | Max concurrent Autotask API calls used to resolve company/resource names on search results. | 3 |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |