# MCP server

> Let Claude, Cursor and other AI clients find, read, create and update your TasksMate tasks — within the scopes you approve.

**What this is:** a Model Context Protocol server that lets an AI assistant or agent work in TasksMate for you. **When you need it:** you want Claude, Cursor or another MCP client to look up, create or update tasks without leaving the conversation.

**Claude Code**


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

**Any MCP client**


**Server URL**

```text
{{MCP_URL}}
```

finalised at 5.1: The server’s public URL — every `{{MCP_URL}}` in this section.

The MCP server speaks to TasksMate only through the API

## What you can do

-   **Find and read work** — search tasks, open one, list yours or a project’s.
-   **Create and change it** — new tasks, status and assignee changes, comments, filing a task under a project.
-   **Stay in control** — the client acts within the scopes you approve, and a task an agent creates waits for a person to review it.

That is 8 tools — see the [tools reference](https://developers.tasksmate.indrasol.com/mcp/tools/).

## Remote or local

The **remote server** is one URL that every client shares, over Streamable HTTP: you add it, sign in to TasksMate, choose your organization and approve the scopes — nothing to install. Clients that can only start a local process use a **stdio package** instead, `npx -y @tasksmate/mcp` or `uvx tasksmate-mcp`, which exposes the same tools and signs in with an access token. Either way the server works through the [TasksMate API](https://developers.tasksmate.indrasol.com/reference/), so the same scopes, rate limits and audit trail apply as to any other integration.

---
Source: https://developers.tasksmate.indrasol.com/mcp/