Tallyfy Workflow Automation

com.tallyfyPublished by tallyfy.comOfficial publisherv1.3.0Updated Nov 1, 2026

Automate tasks, processes, and approvals with AI.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Official remote MCP server for Tallyfy that lets an assistant create and track tasks, run processes, edit templates and forms, and search your organization.

What you can do
  • Create, complete, reassign, comment on and search tasks
  • Launch processes from templates now or on a schedule, advance and track steps
  • Read, create and edit templates and their steps, and read or fill kick-off and step form fields
  • Inspect and manage automation rules, explain step visibility, and list open tasks per step
  • Manage users, groups, guests and organization membership; handle tags, folders, comments and org-wide search
  • Read and upload attached files, search public product docs, keep a per-organization memory document, and call any Tallyfy REST endpoint lacking a dedicated tool
When to use it
Use it when your team runs work in Tallyfy and you want an assistant to act on tasks, processes, templates and forms conversationally, within the signed-in user's permissions. For high-volume or headless batch work, the vendor points to its separate CLI instead.
Requirements
A remote endpoint at mcp.tallyfy.com over streamable HTTP; nothing to host. OAuth sign-in with a Tallyfy account is required, and every request needs a Tallyfy-issued bearer token. Self-hosting is possible with Docker or Python 3.13, optionally pinning a public key via TALLYFY_PUBLIC_KEY.
Before you install
Tools act with the signed-in user's permissions and can write: creating and completing tasks, launching processes, editing templates and form fields, managing people and groups, uploading files, and writing to any REST endpoint via the fallback tool. The server also stores a per-organization memory document. Review write actions before approving them.

Installation

In SourceWeft

  1. Open Tallyfy Workflow Automation in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.tallyfy%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tallyfy-workflow-automation": {
      "type": "http",
      "url": "https://mcp.tallyfy.com/"
    }
  }
}

README

Tallyfy MCP Server

[License: Apache 2.0] [MCP]

The official Model Context Protocol server for Tallyfy, the workflow and process automation platform. It lets any MCP-capable AI assistant run your operations: create and track tasks, launch and advance processes, read and edit templates, fill form fields, manage people and groups, and search across your organization, all through your own authenticated Tallyfy account.

This repository is an automatically published, read-only mirror. The canonical source is maintained privately by Tallyfy and a sanitized, server-only snapshot is published here on every production release. Please do not open pull requests against this mirror (they cannot be merged here). For bugs or feature requests, use the issue tracker or contact us (see Support). Hosting, deployment, and monitoring code is intentionally not part of this mirror.

Connect (hosted, recommended)

Tallyfy runs a managed remote server. You do not need to host anything. Point your MCP client at:

https://mcp.tallyfy.com/

Transport is streamable HTTP and authentication is OAuth against your Tallyfy account, so the assistant only ever sees data the signed-in user is allowed to see.

Example client config
json
{  "mcpServers": {    "tallyfy": {      "type": "streamable-http",      "url": "https://mcp.tallyfy.com/"    }  }}

What it can do

130 tools across the Tallyfy domain, grouped by area:

AreaExamples
Taskscreate, complete, reassign, comment on, and search tasks
Processes (runs)launch a process from a template now or on a schedule, change who a scheduled job runs as, advance and track steps
Templates (checklists)read, create, and edit templates and their steps
Form fieldsread and populate kick-off and step form fields
Automationinspect and manage automated actions / rules, explain why a step in a running process is shown or hidden, and list the open tasks for a step across the processes still running
People & accessusers, groups, guests, organization membership
Organizationtags, folders, comments, search across the org
Filesread and upload files attached to form fields, kickoff fields and task comments
API fallbackread from or write to any Tallyfy REST endpoint that has no dedicated tool
Product docssearch the public Tallyfy documentation index
Org memoryread and update a per-organization memory document held server-side

Almost every tool calls the public Tallyfy API on behalf of the authenticated user (the exceptions read the public docs index and the server-side org memory store). There are no write operations the signed-in user could not perform in the Tallyfy app directly.

Doing bulk or scripted work? This server is tuned for interactive, conversational use and limits how much one request can do at once. For high-volume or headless automation (launching processes from a CSV, exporting every template to disk, multi-org loops, CI/CD approval gates), reach for the first-party tallyfy CLI instead. It is built for deterministic, scriptable batch operations. Install with brew install tallyfy/tap/tallyfy or grab a binary from the releases page.

Run it yourself

You can build and run the server from this mirror with Docker. No configuration is required to start it:

bash
cd serverdocker build -t tallyfy-mcp-server .docker run --rm -p 9000:9000 tallyfy-mcp-servercurl http://localhost:9000/health      # {"status":"healthy"}

The server listens on port 9000 and speaks streamable HTTP at / (and at /mcp). Python 3.13 is required if you prefer to run it without Docker (pip install -r server/requirements.txt, then uvicorn server:app from inside server/).

To configure it, copy .env.example to .env and pass it with --env-file .env. Every value in there is optional; the defaults point at Tallyfy production.

About authentication

Every MCP request needs a Tallyfy-issued OAuth 2.1 bearer token (RS256). The server verifies that signature on every call, so an unauthenticated client gets a 401 challenge and reaches no Tallyfy data. Only /health and the OAuth discovery documents are open.

The verification key is resolved for you. Left alone, the server reads Tallyfy's published JWKS at https://account.tallyfy.com/.well-known/jwks.json and picks up key rotations automatically. Set TALLYFY_PUBLIC_KEY to a PEM public key if you would rather pin it and avoid the network lookup. If neither source resolves, the server still starts, and rejects every token.

Listed on

Security

Tools are scoped to the authenticated user, inputs are validated and the outbound API surface is allowlisted. We disclose no static credentials in this repository: all secrets are supplied at runtime via environment variables. If you find a security issue, please email [email protected] rather than opening a public issue.

Support

License

Apache License 2.0 © Tallyfy, Inc.

Source: README.md at commit 0ac0eaf

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.3.0LatestOct 17, 2026
  2. v1.2.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts