Connect an AI client over MCP.

The connection plus slash commands and workflow skills. Signs in through the browser.

1. 1

   Install the plugin

   Typed inside Claude Code. If the install summary asks, run /reload-plugins.

   textCopy

   /plugin marketplace add AgentTaskLLC/AgentTask-plugin
   /plugin install agent-task@agent-task

2. 2

   Point it at this workspace

   The plugin bundles the production endpoint. If the endpoint above is different, export AGENT_TASK_MCP_URL in the shell that starts Claude Code.

   shellCopy

   export AGENT_TASK_MCP_URL="https://app.agent-task.com/v1/public/mcp"

   claude mcp list prints the resolved URL next to plugin:agent-task:agent-task.

3. 3

   Sign in

   Run /mcp, pick agent-task, and approve the spaces it may reach when the browser opens.

Checked 2026-10-08 against Claude Code docs (MCP, Discover plugins, Plugins reference) + Claude Code 2.1.238 --plugin-dir probe of ${VAR:-default} expansion · vendor docs (opens in a new tab)

Tools only, no slash commands. Uses an API key.

1. 1

   Add the server

   shellCopy

   claude mcp add --transport http agent-task https://app.agent-task.com/v1/public/mcp --header "Authorization: Bearer amk_YOUR_KEY"

   Add --scope user to make it available in every project.

2. 2

   Or commit a project file that reads the key from your environment

   jsonCopy

   {
     "mcpServers": {
       "agent-task": {
         "type": "http",
         "url": "https://app.agent-task.com/v1/public/mcp",
         "headers": { "Authorization": "Bearer ${AGENT_TASK_API_KEY}" }
       }
     }
   }

3. 3

   Check it

   Run /mcp inside Claude Code, or claude mcp list; agent-task should show ✔ Connected.

Checked 2026-10-08 against Claude Code docs — Connect Claude Code to tools via MCP · vendor docs (opens in a new tab)

A custom connector that signs in through the browser. No key needed.

1. 1

   Add a custom connector

   Customize → Connectors → + → Add custom connector, and paste the endpoint. Same path in Claude Desktop and on claude.ai.

   textCopy

   https://app.agent-task.com/v1/public/mcp

   Team and Enterprise: an Owner adds it under Organization settings → Connectors (Custom → Web); members then click Connect. Free plans get one custom connector.

2. 2

   Sign in

   Approve the spaces the connector may reach when the browser opens.

Checked 2026-10-08 against Claude Help Center — Getting started with custom connectors using remote MCP · vendor docs (opens in a new tab)

Copilot Chat in agent mode, through .vscode/mcp.json or the user configuration.

1. 1

   Add the server

   Create .vscode/mcp.json, or run "MCP: Open User Configuration" from the Command Palette. VS Code asks for the key once when the server starts and stores it.

   jsonCopy

   {
     "inputs": [
       {
         "type": "promptString",
         "id": "agent-task-key",
         "description": "Agent Task API key (amk_…)",
         "password": true
       }
     ],
     "servers": {
       "agent-task": {
         "type": "http",
         "url": "https://app.agent-task.com/v1/public/mcp",
         "headers": { "Authorization": "Bearer ${input:agent-task-key}" }
       }
     }
   }

   Watch out: The key is "servers" here and "mcpServers" on github.com.

2. 2

   Start it

   Run "MCP: List Servers", pick agent-task and start it; paste the key at the prompt.

Checked 2026-10-08 against VS Code docs — Use MCP servers in VS Code + MCP configuration reference · vendor docs (opens in a new tab)

Copilot CLI in the terminal.

1. 1

   Add the server

   shellCopy

   copilot mcp add --transport http agent-task https://app.agent-task.com/v1/public/mcp --header "Authorization: Bearer amk_YOUR_KEY"

   Writes ~/.copilot/mcp-config.json (mcpServers, type "http", url, headers, tools ["*"]). Inside the CLI, /mcp add opens the same form.

Checked 2026-10-08 against GitHub Docs — Adding MCP servers for GitHub Copilot CLI · vendor docs (opens in a new tab)

The Copilot cloud agent (formerly coding agent) on github.com, configured per repository.

1. 1

   Store the key as an Agents secret

   Repository → Settings → Secrets and variables → Agents → Secrets → New repository secret, named COPILOT_MCP_AGENT_TASK_KEY.

   Only secrets prefixed COPILOT_MCP_ reach MCP servers.

2. 2

   Add the server to the repository

   Repository → Settings → Copilot → MCP servers → MCP configuration, then Save MCP configuration.

   jsonCopy

   {
     "mcpServers": {
       "agent-task": {
         "type": "http",
         "url": "https://app.agent-task.com/v1/public/mcp",
         "tools": ["*"],
         "headers": { "Authorization": "Bearer $COPILOT_MCP_AGENT_TASK_KEY" }
       }
     }
   }

   Watch out: "type", "url" and "tools" are all required here; ["*"] enables every tool.

   The cloud agent does not support OAuth remote servers, so a key is the only option.

Checked 2026-10-08 against GitHub Docs — Configure MCP servers for your repository (Copilot cloud agent) · vendor docs (opens in a new tab)

Gemini CLI, any tier.

1. 1

   Add the server

   shellCopy

   gemini mcp add --transport http --header "Authorization: Bearer amk_YOUR_KEY" agent-task https://app.agent-task.com/v1/public/mcp

   Writes an httpUrl entry into settings.json; --scope user makes it global. Check with /mcp inside Gemini CLI.

Checked 2026-10-08 against Gemini CLI docs — MCP servers with the Gemini CLI · vendor docs (opens in a new tab)

A custom app in Gemini Spark. Signs in through the browser.

1. 1

   Add a custom app

   gemini.google.com → Settings & help → Connected apps → Custom apps for Spark → Add a custom app, and paste the endpoint.

   textCopy

   https://app.agent-task.com/v1/public/mcp

   Limited rollout: needs Gemini Spark access on a personal Google Account (no work or school accounts), 18+, US, English, and Keep Activity on.

Checked 2026-10-08 against Gemini Apps Help — Connect & manage custom apps for Gemini Spark in the Gemini web app · vendor docs (opens in a new tab)

A URL-only entry; Cursor opens the browser to sign in. No key needed.

1. 1

   Add the server

   ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.

   jsonCopy

   {
     "mcpServers": {
       "agent-task": {
         "url": "https://app.agent-task.com/v1/public/mcp"
       }
     }
   }

2. 2

   Sign in

   Enable it under Customize in the sidebar; approve the spaces when the browser opens.

Checked 2026-10-08 against Cursor docs — Model Context Protocol (MCP), Authentication section · vendor docs (opens in a new tab)

The same file with a bearer key instead of a sign-in.

1. 1

   Add the server

   ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one. No "type" key is needed.

   jsonCopy

   {
     "mcpServers": {
       "agent-task": {
         "url": "https://app.agent-task.com/v1/public/mcp",
         "headers": { "Authorization": "Bearer amk_YOUR_KEY" }
       }
     }
   }

   To keep the key out of the file, write "Bearer ${env:AGENT_TASK_API_KEY}" and export the variable.

2. 2

   Enable it

   Customize in the sidebar lists the server; toggle it on if needed.

Checked 2026-10-08 against Cursor docs — Model Context Protocol (MCP) · vendor docs (opens in a new tab)

Codex CLI, app and IDE extension share ~/.codex/config.toml.

1. 1

   Add the server

   shellCopy

   codex mcp add agent_task --url https://app.agent-task.com/v1/public/mcp --bearer-token-env-var AGENT_TASK_API_KEY

   Export AGENT_TASK_API_KEY in the shell that starts Codex.

2. 2

   Or write the entry yourself

   tomlCopy

   [mcp_servers.agent_task]
   url = "https://app.agent-task.com/v1/public/mcp"
   bearer_token_env_var = "AGENT_TASK_API_KEY"

Checked 2026-10-08 against Codex docs — Model Context Protocol (CLI surface) · vendor docs (opens in a new tab)

A URL-only entry plus codex mcp login. No key needed.

1. 1

   Add the server and sign in

   shellCopy

   codex mcp add agent_task --url https://app.agent-task.com/v1/public/mcp
   codex mcp login agent_task

   Approve the spaces Codex may reach when the browser opens.

Checked 2026-10-08 against Codex docs — Model Context Protocol (CLI surface) · vendor docs (opens in a new tab)

Cascade's MCP configuration file, ~/.codeium/windsurf/mcp_config.json.

1. 1

   Add the server

   Edit the file directly, or open it from the MCPs icon in Cascade.

   jsonCopy

   {
     "mcpServers": {
       "agent-task": {
         "serverUrl": "https://app.agent-task.com/v1/public/mcp",
         "headers": { "Authorization": "Bearer amk_YOUR_KEY" }
       }
     }
   }

   Remote servers take "serverUrl" (or "url"); streamable HTTP is supported.

Checked 2026-10-08 against Windsurf / Devin Desktop docs — Cascade MCP · vendor docs (opens in a new tab)

A remote context server in Zed settings.

1. 1

   Add the context server

   In settings.json (zed: open settings).

   jsonCopy

   {
     "context_servers": {
       "agent-task": {
         "url": "https://app.agent-task.com/v1/public/mcp",
         "headers": { "Authorization": "Bearer amk_YOUR_KEY" }
       }
     }
   }

Checked 2026-10-08 against Zed docs — Model Context Protocol · vendor docs (opens in a new tab)

The same entry without a header; Zed prompts you to sign in.

1. 1

   Add the context server

   jsonCopy

   {
     "context_servers": {
       "agent-task": {
         "url": "https://app.agent-task.com/v1/public/mcp"
       }
     }
   }

2. 2

   Sign in

   Zed prompts to authenticate; approve the spaces when the browser opens.

Checked 2026-10-08 against Zed docs — Model Context Protocol · vendor docs (opens in a new tab)