0.x — pre-release, no compatibility promise yet.What this means

Connect

What this is: adding TasksMate to your AI client. When you need it: once per client — after that the client stays signed in.

{{MCP_URL}}

Authorize — the client sends you to TasksMate. Sign in and choose the organization.
Consent — TasksMate names the client and lists the scopes it asks for. You approve once per client.
Done — the client holds a token and refreshes it itself. Nothing to paste.

Connect once: sign in, approve the scopes, done

Your client

In Settings → Connectors → Add custom connector:

Name: TasksMate
URL:  {{MCP_URL}}

Sign in: You are sent to TasksMate to sign in.

Run in a terminal:

claude mcp add --transport http tasksmate "{{MCP_URL}}"

Sign in: Run /mcp in Claude Code, then choose tasksmate.

In Settings → Connectors → Add custom connector:

Name: TasksMate
URL:  {{MCP_URL}}

Sign in: You are sent to TasksMate to sign in.

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "tasksmate": {
      "url": "{{MCP_URL}}"
    }
  }
}

Sign in: Prompted on first use.

Add to .vscode/mcp.json:

{
  "servers": {
    "tasksmate": {
      "type": "http",
      "url": "{{MCP_URL}}"
    }
  }
}

Sign in: Prompted when the server starts.

Add to .vscode/mcp.json (Copilot Chat, agent mode):

{
  "servers": {
    "tasksmate": {
      "type": "http",
      "url": "{{MCP_URL}}"
    }
  }
}

Sign in: Prompted when the server starts.

Run in a terminal:

codex mcp add tasksmate --url "{{MCP_URL}}"
codex mcp login tasksmate

Sign in: The second line opens the sign-in.

Run in a terminal:

gemini mcp add --transport http tasksmate "{{MCP_URL}}"

Sign in: Run /mcp auth tasksmate in Gemini CLI.

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "tasksmate": {
      "serverUrl": "{{MCP_URL}}"
    }
  }
}

Sign in: Prompted when the server starts.

Add to Zed settings.json:

{
  "context_servers": {
    "tasksmate": {
      "url": "{{MCP_URL}}"
    }
  }
}

Sign in: Prompted when the server starts.

Local (stdio) instead

For a client that starts a local process instead of calling a URL. The package signs in with an access token from Developers → Tokens, scoped to what the client may do.

{
  "mcpServers": {
    "tasksmate": {
      "command": "npx",
      "args": [
        "-y",
        "@tasksmate/mcp"
      ],
      "env": {
        "{{TOKEN_ENV}}": "tm_live_…"
      }
    }
  }
}

{
  "mcpServers": {
    "tasksmate": {
      "command": "uvx",
      "args": [
        "tasksmate-mcp"
      ],
      "env": {
        "{{TOKEN_ENV}}": "tm_live_…"
      }
    }
  }
}

Both packages are pre-release (0.x) until the API declares v1.

Generate it in the app

Developers → MCP writes the artefact for your client, with a Read-only switch and the tool groups it may use (tasks, projects, teams, views, comments, admin — admin off by default). The server enforces both. Copy prompt copies a setup instruction for your agent.

Don’t see your client?

Any client that supports remote MCP servers (Streamable HTTP, OAuth) works with the URL; any other, with a stdio package.