World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 22/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 34/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Autotask. Follow https://mcp.popnx.com/i/wyre-ai-autotask-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 17, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Autotask key (create it on the maker’s site) · 1 setting(s) to fill in (AUTOTASK_USERNAME) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Autotask for Claude on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "autotask": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "AUTOTASK_USERNAME", "-e", "AUTOTASK_SECRET", "-e", "AUTOTASK_INTEGRATION_CODE", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/autotask-mcp:v2.42.0" ], "env": { "AUTOTASK_USERNAME": "your-value", "AUTOTASK_SECRET": "your-value", "AUTOTASK_INTEGRATION_CODE": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTH_MODE, AUTOTASK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Autotask tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
AUTOTASK_USERNAME Autotask API user resource email (e.g. apiuser@example.com)Descriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"autotask": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AUTOTASK_USERNAME",
"-e",
"AUTOTASK_SECRET",
"-e",
"AUTOTASK_INTEGRATION_CODE",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/autotask-mcp:v2.42.0"
],
"env": {
"AUTOTASK_USERNAME": "your-value",
"AUTOTASK_SECRET": "your-value",
"AUTOTASK_INTEGRATION_CODE": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Autotask and tell me what you can do for me, then show me one thing✓ If Claude says it is using Autotask or shows a Autotask tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
AUTOTASK_API_URL Autotask API zone URL — auto-detected per tenant if omittedMCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Autotask yet
Autotask runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Autotask
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Autotask key (create it on the maker’s site) · 1 setting(s) to fill in (AUTOTASK_USERNAME) · Install Docker on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Autotask for Claude Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user autotask --env AUTOTASK_USERNAME=your-value --env AUTOTASK_SECRET=your-value --env AUTOTASK_INTEGRATION_CODE=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e AUTOTASK_USERNAME -e AUTOTASK_SECRET -e AUTOTASK_INTEGRATION_CODE -e AUTH_MODE ghcr.io/wyre-ai/autotask-mcp:v2.42.0 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTH_MODE, AUTOTASK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Autotask tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
AUTOTASK_USERNAME Autotask API user resource email (e.g. apiuser@example.com)Descriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user autotask --env AUTOTASK_USERNAME=your-value --env AUTOTASK_SECRET=your-value --env AUTOTASK_INTEGRATION_CODE=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e AUTOTASK_USERNAME -e AUTOTASK_SECRET -e AUTOTASK_INTEGRATION_CODE -e AUTH_MODE ghcr.io/wyre-ai/autotask-mcp:v2.42.0Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Autotask listed as connected
Use Autotask and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Autotask or shows a Autotask tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
AUTOTASK_API_URL Autotask API zone URL — auto-detected per tenant if omittedMCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Autotask key (create it on the maker’s site) · 1 setting(s) to fill in (AUTOTASK_USERNAME) · Install Docker on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Autotask for Cursor on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "autotask": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "AUTOTASK_USERNAME", "-e", "AUTOTASK_SECRET", "-e", "AUTOTASK_INTEGRATION_CODE", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/autotask-mcp:v2.42.0" ], "env": { "AUTOTASK_USERNAME": "your-value", "AUTOTASK_SECRET": "your-value", "AUTOTASK_INTEGRATION_CODE": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTH_MODE, AUTOTASK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Autotask tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
AUTOTASK_USERNAME Autotask API user resource email (e.g. apiuser@example.com)Descriptions are as written by the maker.
In the Autotask settings, AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTH_MODE, AUTOTASK_USERNAME is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Autotask and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Autotask or shows a Autotask tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
AUTOTASK_API_URL Autotask API zone URL — auto-detected per tenant if omittedMCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Autotask key (create it on the maker’s site) · 1 setting(s) to fill in (AUTOTASK_USERNAME) · Install Docker on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Autotask for VS Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "autotask": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "AUTOTASK_USERNAME", "-e", "AUTOTASK_SECRET", "-e", "AUTOTASK_INTEGRATION_CODE", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/autotask-mcp:v2.42.0" ], "env": { "AUTOTASK_USERNAME": "your-value", "AUTOTASK_SECRET": "your-value", "AUTOTASK_INTEGRATION_CODE": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTH_MODE, AUTOTASK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Autotask tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
AUTOTASK_USERNAME Autotask API user resource email (e.g. apiuser@example.com)Descriptions are as written by the maker.
In the Autotask settings, AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTH_MODE, AUTOTASK_USERNAME is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Autotask and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Autotask or shows a Autotask tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
AUTOTASK_API_URL Autotask API zone URL — auto-detected per tenant if omittedMCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user autotask --env AUTOTASK_USERNAME=your-value --env AUTOTASK_SECRET=your-value --env AUTOTASK_INTEGRATION_CODE=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e AUTOTASK_USERNAME -e AUTOTASK_SECRET -e AUTOTASK_INTEGRATION_CODE -e AUTH_MODE ghcr.io/wyre-ai/autotask-mcp:v2.42.0Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"autotask": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AUTOTASK_USERNAME",
"-e",
"AUTOTASK_SECRET",
"-e",
"AUTOTASK_INTEGRATION_CODE",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/autotask-mcp:v2.42.0"
],
"env": {
"AUTOTASK_USERNAME": "your-value",
"AUTOTASK_SECRET": "your-value",
"AUTOTASK_INTEGRATION_CODE": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"autotask": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AUTOTASK_USERNAME",
"-e",
"AUTOTASK_SECRET",
"-e",
"AUTOTASK_INTEGRATION_CODE",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/autotask-mcp:v2.42.0"
],
"env": {
"AUTOTASK_USERNAME": "your-value",
"AUTOTASK_SECRET": "your-value",
"AUTOTASK_INTEGRATION_CODE": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"autotask": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AUTOTASK_USERNAME",
"-e",
"AUTOTASK_SECRET",
"-e",
"AUTOTASK_INTEGRATION_CODE",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/autotask-mcp:v2.42.0"
],
"env": {
"AUTOTASK_USERNAME": "your-value",
"AUTOTASK_SECRET": "your-value",
"AUTOTASK_INTEGRATION_CODE": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}AUTOTASK_USERNAME required envAUTOTASK_SECRET secret required envAUTOTASK_INTEGRATION_CODE secret required envAUTOTASK_API_URL envMCP_TRANSPORT envAUTH_MODE secret required envLOG_LEVEL envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account WYRE-AI, which owns the repo
Code last changed 2 days ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/wyre-ai-autotask-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTH_MODE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (2.42.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Autotask | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Give your AI assistant direct access to Autotask. Search tickets, create time entries, look up companies, manage projects — all through natural language. No more copy-pasting between browser tabs and chat windows.
This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Autotask PSA environment. Your AI assistant gets 101 tools covering the operations MSP teams use daily: ticket triage, time logging, company lookups, project management, billing review, and more.
If you run an MSP on Autotask and you're tired of the context-switching tax, this is for you.
Part of the [MSP Claude Plugins](https://github.com/WYRE-AI/msp-claude-plugins) ecosystem — a growing suite of AI integrations for the MSP stack including Datto RMM, IT Glue, HaloPSA, ConnectWise Automate, NinjaOne, Huntress, and more. Built by MSPs, for MSPs.
Note — no GitHub Packages token required. Unlike most WYRE MCP servers,
autotask-mcpdoes not depend on a private@wyre-ai/*package on
GitHub Packages. Its only WYRE dependency is the
autotask-nodeSDK, declared
as a git dependency on the public
WYRE-AI/autotask-noderepo, which
npm installresolves anonymously. The DigitalOcean one-click deploy therefore
works without any
NODE_AUTH_TOKEN/GITHUB_TOKENbuild variable.
Claude Desktop — download, open, done:
autotask-mcp.mcpb from the latest releaseNo terminal, no JSON editing, no Node.js install required.
Claude Code (CLI):
claude mcp add autotask-mcp \
-e AUTOTASK_USERNAME=your-user@company.com \ -e AUTOTASK_SECRET=your-secret \ -e AUTOTASK_INTEGRATION_CODE=your-code \ -- npx -y github:WYRE-AI/autotask-mcp
See Installation for Docker and from-source methods.
autotask_get_ticket_details renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Add note" round-trip; neutral theme by default, brandable via MCP_BRAND_* env vars. In every host, the text the assistant reads carries the full ticket: description, contact, linked configuration item, custom fields (UDFs), recent notes and the complete record as JSONThe simplest method — no terminal, no JSON editing, no Node.js install required.
autotask-mcp.mcpb from the latest releaseFor Claude Code (CLI), one command:
claude mcp add autotask-mcp \
-e AUTOTASK_USERNAME=your-user@company.com \ -e AUTOTASK_SECRET=your-secret \ -e AUTOTASK_INTEGRATION_CODE=your-code \ -- npx -y github:WYRE-AI/autotask-mcp
Local (stdio — for Claude Desktop or Claude Code):
{
"mcpServers": { "autotask": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "MCP_TRANSPORT=stdio", "-e", "AUTOTASK_USERNAME=your-user@company.com", "-e", "AUTOTASK_SECRET=your-secret", "-e", "AUTOTASK_INTEGRATION_CODE=your-code", "--entrypoint", "node", "ghcr.io/wyre-ai/autotask-mcp:latest", "dist/entry.js" ] } } }
Remote (HTTP Streamable — for server deployments):
docker run -d \
--name autotask-mcp \ -p 127.0.0.1:8080:8080 \ -e CONDUIT_S2S_SECRET="your-real-s2s-secret" \ -e AUTOTASK_USERNAME="your-user@company.com" \ -e AUTOTASK_SECRET="your-secret" \ -e AUTOTASK_INTEGRATION_CODE="your-code" \ --restart unless-stopped \ ghcr.io/wyre-ai/autotask-mcp:latest
curl http://127.0.0.1:8080/health
The HTTP server refuses to start when CONDUIT_S2S_SECRET is empty or a known placeholder. Clients connect to http://127.0.0.1:8080/mcp using MCP Streamable HTTP transport and must send X-Gateway-S2S. See X-Gateway-S2S signing.
Gateway Mode (for MCP Gateway deployments):
When deploying behind an MCP Gateway that injects credentials via HTTP headers. This container has no static Autotask credentials:
docker run -d \
--name autotask-mcp \ -p 127.0.0.1:8080:8080 \ -e CONDUIT_S2S_SECRET="your-real-s2s-secret" \ -e AUTH_MODE=gateway \ --restart unless-stopped \ ghcr.io/wyre-ai/autotask-mcp:latest
The gateway injects credentials via headers:
X-Gateway-S2S: service-to-service proof (required on /mcp)X-API-Key: Autotask usernameX-API-Secret: Autotask secretX-Integration-Code: Autotask integration codeX-Impersonation-Resource-Id: (optional) Autotask resource ID to act on behalf ofA /mcp request missing any of the three Autotask headers returns 401 and does not fall back to AUTOTASK_* in the environment. See Gateway Mode for details.
git clone https://github.com/WYRE-AI/autotask-mcp.git
cd autotask-mcp npm ci && npm run build
Then point your MCP client at dist/entry.js:
{
"mcpServers": { "autotask": { "command": "node", "args": ["/path/to/autotask-mcp/dist/entry.js"], "env": { "AUTOTASK_USERNAME": "your-user@company.com", "AUTOTASK_SECRET": "your-secret", "AUTOTASK_INTEGRATION_CODE": "your-code" } } } }
Create a .env file with your configuration:
# Required Autotask API credentials (Local Mode)
AUTOTASK_USERNAME=your-api-user@example.com AUTOTASK_SECRET=your-secret-key AUTOTASK_INTEGRATION_CODE=your-integration-code
MCP_SERVER_NAME=autotask-mcp
AUTH_MODE=env # env (local), gateway (hosted)
CONDUIT_S2S_SECRET=
MCP_TRANSPORT=stdio # stdio, http MCP_HTTP_PORT=8080 # HTTP transport port (only used when MCP_TRANSPORT=http)
MCP_HTTP_HOST=0.0.0.0 # HTTP transport bind address
LOG_LEVEL=info # error, warn, info, debug LOG_FORMAT=simple # simple, json
AUTOTASK_ENHANCE_CONCURRENCY=3
AUTOTASK_MAX_INFLIGHT=3
NODE_ENV=production
When deployed behind an MCP Gateway (e.g., mcp.wyre.ai), the server operates in gateway mode where credentials are injected via HTTP headers on each request.
Enable Gateway Mode:
AUTH_MODE=gateway
MCP_TRANSPORT=http CONDUIT_S2S_SECRET=
Every /mcp request must include a valid X-Gateway-S2S header and the three Autotask credential headers. A request missing any credential header returns 401. The server does not fall back to AUTOTASK_USERNAME, AUTOTASK_SECRET, or AUTOTASK_INTEGRATION_CODE in the process environment.
Expected Headers:
| Header | Description |
|---|---|
X-Gateway-S2S | Service-to-service proof. t= ,v1= . Required on /mcp whenever CONDUIT_S2S_SECRET is set. See X-Gateway-S2S signing. |
X-API-Key | Autotask API username (email) |
X-API-Secret | Autotask API secret key |
| X-Integration-Code | Autotask integratio