Connect AI clients to Taskie

This guide shows where and how to register Taskie in each AI editor and agent. Every client's steps were checked against that tool's official documentation in November 2026; if a vendor moves its menus, follow the official docs link under each section.

Before you start

In Taskie, go to Settings → Connections & MCP and click Connect a client (or Connect another client). In the window that opens, pick your client to see the server URL, the steps and a ready-made configuration for that client only. On a phone the same window opens as a bottom sheet.

• Browser sign-in (recommended): you only give the client the server URL. When it connects, a Taskie page opens where you choose the workspace and access level. Nothing to create or copy.
• Manual token: for clients without browser sign-in, or places with no browser such as SSH and cloud agents. Click Create token in the connect window; the token is shown once and filled into the configuration for you.
• Other: for any MCP client, script or curl call that is not listed. You get the generic mcpServers configuration and a curl command to test the connection.

Claude

Claude on the web, desktop and mobile. Add Taskie once as a custom connector and it works in every Claude app.

Connect with browser sign-in

1. In Claude, open Customize › Connectors (newer accounts call it Plugins), click + Add, then Add custom connector.
2. Enter Taskie as the name, paste the server URL and click Continue.
3. For the OAuth client choose Register automatically, then click Add.
4. Click Connect and approve access in the Taskie window that opens. In a chat, turn Taskie on from + › Connectors.
5. On Team and Enterprise plans an owner adds the connector first under Organization settings › Connectors; members then only click Connect.

Anthropic documentation: support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

ChatGPT

ChatGPT on the web. Taskie is added as a custom MCP plugin; availability depends on your plan, and on Business workspaces only admins can add it.

Connect with browser sign-in

1. Open chatgpt.com/plugins on the web, click +, then Add custom MCP server.
2. Enter Taskie as the name and paste the server URL under Connection.
3. Set authentication to OAuth, confirm the warning and click Create as a plugin.
4. Install the plugin and approve access in the Taskie window. In a chat, type @ and pick Taskie; ChatGPT asks before every change.

OpenAI documentation: help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt

Claude Code

Anthropic's coding agent in the terminal and IDEs. One command adds Taskie.

Connect with browser sign-in

1. Run the command below in your terminal. Add --scope user to use Taskie in every project.
2. Start Claude Code, run /mcp, select taskie and choose Authenticate (or run claude mcp login taskie).
3. Approve access in the browser window that opens.

Connect with a token

1. Run the command below in your terminal; it already carries your token.
2. Run /mcp in Claude Code and check that taskie is connected.
3. While a token header is set, Claude Code skips browser sign-in. Remove the server and add it again without the header to switch.

Anthropic documentation: code.claude.com/docs/en/mcp

Cursor

AI code editor. Taskie goes into Cursor's mcp.json, for all projects or just one.

Connect with browser sign-in

1. Paste the configuration below into ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
2. Save the file, restart Cursor, then open Customize › MCPs and check that taskie is on.
3. The first time Cursor connects it opens the Taskie sign-in page; approve access there.

Connect with a token

1. Paste the configuration below into ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
2. Save the file, restart Cursor, then open Customize › MCPs and check that taskie is on.
3. If the tools don't show up, open the Output panel and pick MCP Logs.

Cursor documentation: cursor.com/docs/mcp

VS Code

VS Code's built-in agent chat. The default Copilot agent reads servers from ~/.copilot/mcp-config.json.

Connect with browser sign-in

1. Run MCP: Add Server from the Command Palette, choose HTTP, paste the server URL, name it taskie and pick Copilot Global. Or paste the configuration below into ~/.copilot/mcp-config.json.
2. When VS Code asks to sign in, allow it and approve access in the Taskie window.
3. In chat, open the tools menu and check that the Taskie tools are on.

Connect with a token

1. Paste the configuration below into ~/.copilot/mcp-config.json (or .mcp.json in the workspace root).
2. Reload VS Code, run MCP: List Servers and check that taskie is running.
3. Don't put the token in an input variable: the default Copilot agent skips servers that need one.

Microsoft documentation: code.visualstudio.com/docs/agent-customization/mcp-servers

Codex

OpenAI Codex. The CLI, the IDE extension and the ChatGPT desktop app share one config file.

Connect with browser sign-in

1. Run codex mcp add taskie --url followed by the server URL, or paste the configuration below into ~/.codex/config.toml.
2. Run codex mcp login taskie. In the desktop app or IDE extension, click Authenticate next to taskie instead.
3. Approve access in the browser, then run /mcp to see the Taskie tools.

Connect with a token

1. Paste the configuration below into ~/.codex/config.toml.
2. Restart Codex (or the IDE extension) and run /mcp to check the connection.

OpenAI documentation: learn.chatgpt.com/docs/extend/mcp

Gemini CLI

Google's Gemini CLI. Browser sign-in needs a browser on the same machine, so use a token over SSH.

Connect with browser sign-in

1. Run gemini mcp add --transport http -s user taskie followed by the server URL, or paste the configuration below into ~/.gemini/settings.json.
2. Start gemini. The browser opens for sign-in; if it doesn't, run /mcp auth taskie.
3. Approve access, then run /mcp to list the Taskie tools.

Connect with a token

1. Paste the configuration below into ~/.gemini/settings.json (or .gemini/settings.json in a project).
2. Restart gemini and run /mcp to check that taskie is connected.

Google documentation: geminicli.com/docs/tools/mcp-server/

Copilot CLI

GitHub Copilot CLI. For Copilot inside VS Code pick VS Code; in JetBrains, Eclipse and Xcode, put the token under requestInit.headers in mcp.json.

Connect with browser sign-in

1. Run the command below in your terminal.
2. Start copilot. If taskie shows as needing sign-in, run /mcp auth taskie.
3. Approve access in the browser window that opens.

Connect with a token

1. Run the command below in your terminal; it already carries your token.
2. Start copilot and run /mcp to check that taskie is connected.
3. On Business and Enterprise plans an admin must first turn on the MCP servers in Copilot policy.

GitHub documentation: docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers

Devin Desktop

Devin Desktop is the new name of Windsurf. Its Devin Local agent reads MCP servers from mcp_config.json.

Connect with browser sign-in

1. Run devin mcp add -s user taskie followed by the server URL, or paste the configuration below into ~/.config/devin/mcp_config.json.
2. Open Customize › MCPs and check that taskie is listed.
3. The first time taskie is used, approve access in the browser (or run devin mcp login taskie).

Connect with a token

1. Paste the configuration below into ~/.config/devin/mcp_config.json.
2. Open Customize › MCPs and check that taskie is connected.

Cognition documentation: docs.devin.ai/cli/extensibility/mcp/configuration

Zed

Zed editor. Browser sign-in needs Zed 0.230 or later.

Connect with browser sign-in

1. Open Settings › AI › MCP Servers, click Add Server › Add Remote Server and enter the server URL, or paste the configuration below into settings.json.
2. Click Authenticate when Zed asks and approve access in the browser.
3. A green dot next to taskie means it is active; use it from the Agent Panel.

Connect with a token

1. Paste the configuration below into Zed's settings.json (zed: open settings file).
2. Check Settings › AI › MCP Servers: a green dot next to taskie means it is active.

Zed Industries documentation: zed.dev/docs/ai/mcp

JetBrains AI Assistant

AI Assistant in IntelliJ IDEA, PyCharm and the other JetBrains IDEs. JetBrains doesn't document browser sign-in for MCP, so connect with a token.

Connect with a token

1. Open Settings › Tools › AI Assistant › Model Context Protocol (MCP) and click + Add.
2. Choose HTTP, paste the configuration below and pick Global or the current project.
3. Click OK, then Apply, and check the Status column for taskie.

JetBrains documentation: www.jetbrains.com/help/ai-assistant/mcp.html

Junie

JetBrains' coding agent, as an IDE plugin and as Junie CLI.

Connect with browser sign-in

1. Open Settings › Tools › Junie › MCP Settings, click + and paste the configuration below (or edit ~/.junie/mcp/mcp.json).
2. taskie shows Authorization required: in Junie CLI run /mcp, select taskie and choose Authorize.
3. Approve access in the browser; the status changes to Active.

Connect with a token

1. Open Settings › Tools › Junie › MCP Settings, click + and paste the configuration below (or edit ~/.junie/mcp/mcp.json).
2. Check that taskie is Active and its tools are listed.

JetBrains documentation: junie.jetbrains.com/docs/junie-cli-mcp-configuration.html

Antigravity

Google Antigravity (app, IDE and CLI). Sign-in ends with a code you copy back into Antigravity.

Connect with browser sign-in

1. In the agent panel open … › MCP Servers › Manage MCP Servers › View raw config and paste the configuration below.
2. Open Agent settings (Cmd/Ctrl + ,), go to Customizations and click Authenticate next to taskie.
3. Approve access in the browser, copy the code it shows, paste it back into Antigravity and click Submit.

Connect with a token

1. In the agent panel open … › MCP Servers › Manage MCP Servers › View raw config and paste the configuration below.
2. Refresh the MCP servers and check that taskie is connected.

Google documentation: antigravity.google/docs/mcp

TRAE

TRAE IDE and Agent. Browser sign-in for MCP needs TRAE 3.5.51 or later.

Connect with browser sign-in

1. Open Settings › MCP, click Add › Create Manually, paste the configuration below and click Confirm.
2. In the Agent window, pick Local or Cloud to match where your tasks run.
3. When TRAE asks to authorize taskie, approve access in the browser.

Connect with a token

1. Open Settings › MCP, click Add › Create Manually, paste the configuration below and click Confirm.
2. In the Agent window, pick Local or Cloud to match where your tasks run.

ByteDance documentation: docs.trae.ai/ide/add-mcp-servers

OpenCode

OpenCode terminal agent. Versions 1 and 2 both read this configuration.

Connect with browser sign-in

1. Paste the configuration below into ~/.config/opencode/opencode.json or your project's opencode.json.
2. Run opencode mcp auth taskie (in OpenCode 2 you can also open /mcps and sign in).
3. Approve access in the browser.

Connect with a token

1. Paste the configuration below into ~/.config/opencode/opencode.json or your project's opencode.json.
2. Run opencode mcp list and check that taskie is connected.

OpenCode documentation: opencode.ai/docs/mcp-servers/

Cline

Cline extension for VS Code, plus the Cline CLI.

Connect with browser sign-in

1. Click the MCP Servers icon in the Cline panel and open Remote Servers.
2. Enter taskie as the name, paste the server URL, pick Streamable HTTP and click Add Server.
3. On the Configure tab, click Authenticate next to taskie and approve access in the browser.

Connect with a token

1. Click the MCP Servers icon in the Cline panel, open Configure and click Configure MCP Servers.
2. Paste the configuration below and save.
3. Check that taskie turns green on the Configure tab.

Cline documentation: docs.cline.bot/mcp/mcp-overview

Kilo Code

Kilo Code extension and CLI. Current versions keep MCP servers in kilo.jsonc.

Connect with browser sign-in

1. Open Settings › Agent Behaviour › MCP Servers and click Add Server, or paste the configuration below into ~/.config/kilo/kilo.jsonc.
2. When the needs-auth notice appears, click it (or run kilo mcp auth).
3. Approve access in the browser.

Connect with a token

1. Paste the configuration below into ~/.config/kilo/kilo.jsonc (or kilo.jsonc in your project).
2. Check under Settings › Agent Behaviour › MCP Servers that taskie is connected.

Kilo documentation: kilo.ai/docs/features/mcp/using-mcp-in-kilo-code

goose

goose, the open-source agent for desktop and terminal. It reads YAML, not the usual mcpServers JSON.

Connect with browser sign-in

1. In goose Desktop open Extensions › Add custom extension, choose Streamable HTTP, name it taskie and paste the server URL as the Endpoint. Or paste the YAML below into ~/.config/goose/config.yaml.
2. Click Add; a browser opens for you to approve access.

Connect with a token

1. In goose Desktop open Extensions › Add custom extension, choose Streamable HTTP, paste the server URL as the Endpoint and add the Authorization header under Request Headers. Or paste the YAML below into ~/.config/goose/config.yaml.
2. Click Add and start a new session.

Agentic AI Foundation documentation: goose-docs.ai/docs/getting-started/using-extensions

Amp

Amp coding agent. Its settings use the amp.mcpServers key.

Connect with browser sign-in

1. Run amp mcp add taskie followed by the server URL, or paste the configuration below into ~/.config/amp/settings.json.
2. Start Amp; the Taskie sign-in page opens in your browser. Approve access there.

Connect with a token

1. Paste the configuration below into ~/.config/amp/settings.json.
2. Start Amp and check that the Taskie tools are available.

Amp documentation: ampcode.com/docs/customize/mcp

Warp

Warp's terminal agents. Cloud agents can't finish a browser sign-in, so use a token for them.

Connect with browser sign-in

1. Open Settings › Agents › MCP servers and click + Add.
2. Paste the configuration below and save.
3. Start taskie; a browser opens for you to approve access.

Connect with a token

1. Open Settings › Agents › MCP servers and click + Add.
2. Paste the configuration below and save.
3. Start taskie and check that it is running.

Warp documentation: docs.warp.dev/agents/capabilities/mcp/

Conductor

Conductor runs Claude Code and Codex agents and uses their MCP settings; it has no server list of its own.

Connect with browser sign-in

1. Add Taskie to Claude Code with the command below (for Codex sessions, follow the Codex steps instead).
2. In a Conductor workspace, open MCP status from the plug icon (or run /mcp-status) and click Refresh status.
3. Use the sign-in action on the taskie row, approve access, then start a new session.

Connect with a token

1. Add Taskie to Claude Code with the command below (for Codex sessions, follow the Codex steps instead).
2. In a Conductor workspace, open MCP status from the plug icon (or run /mcp-status) and click Refresh status.
3. Start a new session so the Taskie tools load.

Conductor documentation: www.conductor.build/docs/guides/configure-mcp-servers

ZCode

ZCode, Z.ai's desktop agent for the GLM models. Using the GLM Coding Plan inside another agent? Pick that agent instead.

Connect with browser sign-in

1. Open Settings › MCP Servers and click New MCP Server.
2. Pick a scope, set the type to HTTP, name it taskie and paste the server URL (or switch to Full configuration and paste the JSON below).
3. Click Add, then click Open authorization on the taskie row and approve access in the browser.

Connect with a token

1. Open Settings › MCP Servers and click New MCP Server.
2. Pick a scope, set the type to HTTP, name it taskie, paste the server URL and add the Authorization header under Headers (or paste the JSON below in Full configuration).
3. Click Add and check that taskie connects.

Z.ai documentation: zcode.z.ai/en/docs/mcp-services

Kimi Code

Kimi Code CLI from Moonshot AI, which replaced the archived Kimi CLI.

Connect with browser sign-in

1. Run /mcp-config in Kimi Code to add taskie, or paste the configuration below into ~/.kimi-code/mcp.json.
2. Run /mcp-config login taskie and approve access in the browser.
3. Run /mcp to check the connection.

Connect with a token

1. Paste the configuration below into ~/.kimi-code/mcp.json.
2. Run /mcp in Kimi Code to check the connection.

Moonshot AI documentation: moonshotai.github.io/kimi-code/en/customization/mcp.html

Qwen Code

Qwen Code CLI. Qwen's docs don't cover automatic browser sign-in yet, so connect with a token.

Connect with a token

1. Paste the configuration below into ~/.qwen/settings.json (or .qwen/settings.json in a project).
2. Restart qwen and run /mcp to check that taskie is connected.

Qwen documentation: qwenlm.github.io/qwen-code-docs/en/users/features/mcp/

Replit

Replit Agent. Servers added here are available in all your Replit projects.

Connect with browser sign-in

1. Open replit.com/integrations and, under MCP Servers, click + Add MCP server (or open the one-click install link below).
2. Enter Taskie as the display name and paste the server URL.
3. Click Test & save and approve access in the Taskie window.

Connect with a token

1. Open replit.com/integrations and, under MCP Servers, click + Add MCP server.
2. Enter Taskie as the display name, paste the server URL, then open Advanced settings and add the Authorization header below.
3. Click Test & save.

Replit documentation: docs.replit.com/build/connect-via-mcp

If the connection doesn't work

• The tools don't show up: quit and reopen the client, or refresh the taskie server in that client's MCP settings. Most clients only read their configuration at start-up.
• No browser opened for sign-in: many clients start sign-in from a button or command such as Authenticate or login; see that client's steps. Over SSH or in a cloud agent, use a token.
• 401 error: the token expired or was deactivated. Open the connection under Connections & MCP and regenerate the token, or sign in through the browser again.
• The client tries both methods: when an Authorization header is set, some clients skip browser sign-in. Keep one method per connection.

To manage connections, access levels and security, see Connect an external client to Taskie with MCP, and for tool controls see MCP tools and safety.