# Tallyfy MCP server

> Run Tallyfy workflows from chat: launch processes, manage tasks and templates, fill form fields and search your organization.

- Listing: https://mcp.tc/i/tallyfy
- Connect: use the server's own URL `https://mcp.tallyfy.com/` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Productivity & Projects](https://mcp.tc/c/productivity)
- Vendor: Tallyfy
- Homepage: <https://tallyfy.com/products/pro/integrations/mcp-server/>
- Docs: <https://tallyfy.com/products/pro/integrations/mcp-server/>
- Repository: <https://github.com/tallyfy/mcp-public>

## About

Connects an AI assistant to Tallyfy, the workflow and process automation platform. You can create, complete, reassign and search tasks, launch processes from templates, read and edit templates and their steps, fill form fields, manage users and groups, and search across your organization. A fallback tool reaches any Tallyfy REST endpoint without a dedicated tool, and other tools search the public docs and keep a per-organization memory document.

Runs as a hosted streamable HTTP endpoint at https://mcp.tallyfy.com/. Users sign in to their Tallyfy account with OAuth, and the assistant only sees data that user can access. The Apache-2.0 server source can also be built with Docker or run with Python 3.13.

## What it can do

- Create, complete, reassign, comment on and search tasks
- Launch processes from templates and track their steps
- Read, create and edit templates and their steps
- Read and populate kick-off and step form fields
- Inspect and manage automation rules
- Manage users, groups and guests
- Manage tags and folders and search the organization
- Call any Tallyfy REST endpoint through an API fallback

## Example prompts

- "Launch the Onboarding template for Jane Doe"
- "Show my open tasks that are due this week"
- "Add an approval step to the Invoice Review template"
- "Which processes are currently running for the sales team?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http tallyfy https://mcp.tallyfy.com/
```

2. Start Claude Code, type `/mcp`, pick **tallyfy** and choose **Authenticate**. A browser window opens for the Tallyfy sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Tallyfy** and paste this URL:

```url
https://mcp.tallyfy.com/
```

3. Click **Add**, then **Connect**, and sign in when Tallyfy asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Tallyfy&connectorUrl=https%3A%2F%2Fmcp.tallyfy.com%2F>) (opens connector settings)

2. Check that the URL reads `https://mcp.tallyfy.com/` and click **Add**.

3. Click **Connect** and sign in when Tallyfy asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.tallyfy.com/` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Tallyfy to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=tallyfy&config=eyJ1cmwiOiJodHRwczovL21jcC50YWxseWZ5LmNvbS8ifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "tallyfy": {
      "url": "https://mcp.tallyfy.com/"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=tallyfy&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tallyfy.com%2F%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"tallyfy","type":"http","url":"https://mcp.tallyfy.com/"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "tallyfy": {
      "type": "http",
      "url": "https://mcp.tallyfy.com/"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "tallyfy": {
      "serverUrl": "https://mcp.tallyfy.com/"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add tallyfy --url https://mcp.tallyfy.com/
codex mcp login tallyfy
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.tallyfy]
url = "https://mcp.tallyfy.com/"
```

### Gemini CLI

```bash
gemini mcp add --transport http tallyfy https://mcp.tallyfy.com/
```

Then, inside Gemini CLI, run `/mcp auth tallyfy` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "tallyfy": {
      "type": "http",
      "url": "https://mcp.tallyfy.com/"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.tallyfy.com/`.

## Recent changes

- 2026-10-17 23:01 UTC: New version 1.3.0 (was 1.2.0), reported by the server. Source: automatic check.
- 2026-10-07 22:50 UTC: Tracking started: version 1.2.0. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/tallyfy#history (Atom feed: https://mcp.tc/i/tallyfy/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.3.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-05
- Updated: 2026-10-05

---
Source: https://mcp.tc/i/tallyfy (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
