Claude integration

Integration status

This integration is live. The Tallyfy MCP server at https://mcp.tallyfy.com supports OAuth 2.1 with PKCE. Use Streamable HTTP transport - SSE is no longer supported.

Connect Claude to Tallyfy through MCP

Both Claude.ai (web) and Claude Desktop connect to Tallyfy through the MCP server¹ at https://mcp.tallyfy.com. Once connected, Claude can read your tasks, processes, templates, and team members - then take actions on your behalf using natural language.

The connection uses OAuth 2.1 with PKCE². Claude handles the auth flow automatically when you add the server URL. You just sign in with your Tallyfy credentials and authorize access.

Option 1: Claude.ai web (browser)

Available on paid Claude plans (Pro, Max, Team, Enterprise). Once added, the connector syncs across Claude web, Claude Desktop, and Claude Mobile.

1. Open Claude.ai settings

   Go to claude.ai ↗ and click your profile icon in the top-left corner, then select Settings.

2. Go to Connectors

   In Settings, click Connectors in the left sidebar.

3. Add a custom connector

   Click Add custom connector. Enter:

   • Name: Tallyfy
   • URL: https://mcp.tallyfy.com

   Then click Save.

4. Authorize with your Tallyfy account

   Claude.ai opens a browser window to Tallyfy’s authorization page. Sign in with your Tallyfy credentials and click Authorize to grant Claude access to your organization.

5. Verify the connection

   Start a new conversation. The Tallyfy connector appears in your active integrations. Try:

   What are my open tasks in Tallyfy?

   Claude calls get_my_tasks and returns your current task list.

Option 2: Claude Desktop app

Available on paid Claude plans (Pro, Max, Team, Enterprise). Download for macOS or Windows.

1. Install or update Claude Desktop

   Download from claude.ai/download ↗. Remote MCP server support with OAuth requires a recent version.

2. Open settings

   Launch Claude Desktop, then open Settings. On macOS use Cmd+, or click the Claude menu - then Settings. On Windows use the gear icon or the application menu.

3. Go to Integrations

   Navigate to the Integrations tab (labelled Extensions or MCP servers in some versions).

4. Add the Tallyfy MCP server

   Click Add integration, Add remote server, or the + button. Enter:

   https://mcp.tallyfy.com

   Claude Desktop discovers the OAuth endpoints automatically - no manual configuration needed.

5. Authorize with your Tallyfy account

   Claude Desktop opens a browser window to Tallyfy’s authorization page. Sign in and click Authorize. The token is stored in your OS keychain (macOS Keychain or Windows Credential Manager) - never in plaintext.

6. Restart Claude Desktop

   Quit completely (Cmd+Q on macOS) and relaunch. This ensures the MCP connection initializes cleanly.

7. Verify the connection

   Open a new conversation. Look for the tools icon at the bottom of the chat input - clicking it shows available Tallyfy tools. Try:

   What are my open tasks in Tallyfy?

   Claude calls get_my_tasks and returns your current task list.

How Claude integration works

Tallyfy’s MCP server runs on Cloudflare at https://mcp.tallyfy.com and exposes your Tallyfy data as tools Claude can call during a conversation.

The flow works like this:

1. Tool discovery - Claude connects and queries the MCP server for available tools
2. OAuth 2.1 authentication - Claude handles the auth flow. You sign in with Tallyfy credentials and authorize access
3. Tool calls - When you ask a question, Claude picks the right Tallyfy tool and passes the correct parameters
4. API execution - The MCP server uses your credentials to call the Tallyfy API and returns structured results
5. Response - Claude formats the data into a natural language answer

Authentication architecture

The MCP server uses OAuth 2.1 with PKCE (S256). All discovery and token exchange happens through https://mcp.tallyfy.com, which proxies to Tallyfy’s authorization server:

Endpoint	URL
MCP server	https://mcp.tallyfy.com
Protected resource metadata	https://mcp.tallyfy.com/.well-known/oauth-protected-resource
Authorization server metadata	https://mcp.tallyfy.com/.well-known/oauth-authorization-server
Authorization (proxy)	https://mcp.tallyfy.com/mcp/oauth/authorize
Token exchange (proxy)	https://mcp.tallyfy.com/mcp/oauth/token
Client registration (proxy)	https://mcp.tallyfy.com/mcp/oauth/register
JWKS (token verification)	https://mcp.tallyfy.com/.well-known/jwks.json

Supported OAuth scopes:

Scope	Access
mcp.tasks.read	Read tasks and assignments
mcp.tasks.write	Create, update, and complete tasks
mcp.processes.read	Read workflow runs
mcp.processes.write	Launch, update, and archive processes
mcp.templates.read	Read templates and steps
mcp.templates.write	Edit templates, steps, and automations
mcp.forms.read	Read form fields
mcp.forms.write	Add and modify form fields
mcp.users.read	Read organization members and guests
mcp.users.write	Invite and manage users
mcp.automation.read	Read automation rules
mcp.automation.write	Create and modify automations

MCP server tools

The Tallyfy MCP server exposes these tools to Claude:

Task tools

• get_my_tasks - Get all tasks assigned to the current user
• get_user_tasks - Get tasks for a specific team member by user ID
• get_tasks_for_process - Get all tasks in a specific process by ID or name
• create_task_from_text - Create a task from natural language - extracts title, deadline, and assigns to named members or guests
• complete_task - Mark a task as complete
• reopen_task - Reopen a previously completed task
• update_task - Update task properties like title, deadline, or description

Search tools

• search_for_tasks - Search tasks across the organization by keyword
• search_for_processes - Search workflow processes/runs by keyword
• search_for_templates - Search templates by keyword (use get_all_templates for a full list)

Process tools

• get_organization_runs - Get all active workflow processes with optional filters for status, template, owner, tags, and type
• launch_process - Launch a new process from a template with a name and optional tags/folders
• get_process - Get details for a specific process by ID
• update_process - Update process properties like name or tags
• archive_process - Archive a completed or cancelled process

Template tools

• get_template - Get a template by ID or name with full details
• get_all_templates - Get all templates in the organization
• get_template_steps - Get all steps for a template
• get_kickoff_fields - Get kick-off form fields for a template
• get_step_dependencies - Analyze which automations control when a step appears
• assess_template_health - Health check covering step clarity, form fields, automations, and deadlines
• suggest_step_deadline - Get deadline recommendations for a step based on its type and complexity
• suggest_kickoff_fields - Get suggested kick-off fields based on template content
• add_step_to_template - Add a new step to an existing template
• add_assignees_to_step - Add member or guest assignees to a step
• edit_description_on_step - Update the description/instructions on a step
• update_template - Update template properties like title or description
• clone_template - Create a copy of an existing template with a new name

Form field tools

• add_form_field_to_step - Add text, dropdown, date, or other field types to a step
• update_form_field - Update an existing form field’s properties
• move_form_field - Reorder a form field within a step
• delete_form_field - Remove a form field from a step
• get_dropdown_options - Get options for a dropdown field
• update_dropdown_options - Update dropdown choices
• suggest_form_fields_for_step - Get AI recommendations for useful form fields based on step content

Automation tools

• create_automation_rule - Create if-then automation rules on a template
• update_automation_rule - Modify an existing automation rule’s conditions or actions
• delete_automation_rule - Remove an automation rule
• analyze_template_automations - Analyze all automations for conflicts and redundancies
• get_step_visibility_conditions - See which automations control a step’s visibility
• suggest_automation_consolidation - Get AI recommendations for simplifying automation rules
• consolidate_automation_rules - Preview or apply automation consolidation changes

Comment tools

• get_task_comments - Get all comments on a specific task
• add_task_comment - Add a comment to a task

User and guest tools

• get_organization_users - Get all organization members with profile data
• get_organization_users_list - Get members with minimal data for listing
• get_organization_guests - Get guest users with full data
• get_organization_guests_list - Get guests with minimal data
• invite_user_to_organization - Invite a new member by email

Organization tools

• get_groups - Get groups in the organization
• get_folders - Get folders for organizing templates and processes
• get_tags - Get tags used across the organization

Practical examples

Template health audit

Prompt: "Assess the health of our Customer Onboarding template and
suggest improvements to the automation rules."

Claude calls: assess_template_health -> analyze_template_automations ->
suggest_automation_consolidation, then summarizes findings and
recommended fixes.

Process launch and tracking

Prompt: "Launch the Employee Onboarding template for Jane Doe and
show me all the tasks that were created."

Claude calls: launch_process -> get_tasks_for_process, then lists
every task with assignees and deadlines.

Writing effective prompts for Claude

Be specific about what you want analyzed and how you want the output structured:

Good: "Analyze the proposal considering technical feasibility, financial
viability, strategic alignment, and risk factors. Provide weighted scoring
for each dimension with detailed justification."

Bad: "Review the proposal and approve or reject."

Give Claude explicit reasoning steps:

Good: "First, identify all people affected. Second, analyze impact
on each group. Third, recommend mitigation strategies. Finally, provide
an implementation timeline."

Bad: "Figure out who this affects and what to do."

Security and compliance

• No training on your data - Anthropic does not train on API inputs
• JWT validation - Tokens validated via RS256 using Tallyfy’s public key. Only Tallyfy can issue valid tokens
• OS keychain storage - Claude Desktop stores tokens in macOS Keychain or Windows Credential Manager, never in plaintext
• Data isolation - Each organization’s data stays separate
• Audit logging - Complete interaction history
• SOC 2 Type II - Anthropic maintains compliance

Troubleshooting

“MCP tools icon doesn’t appear”

• Restart Claude Desktop completely (Cmd+Q on macOS, not just closing the window)
• Check Settings - then Integrations to confirm https://mcp.tallyfy.com is listed and active
• If the server shows an error, remove and re-add it

“Authorization fails or loops”

• Confirm you’re signing in with the Tallyfy account that has access to the target organization
• Open https://mcp.tallyfy.com/.well-known/oauth-protected-resource in your browser - a JSON response means the server is reachable
• Clear Claude Desktop’s stored credentials and re-authorize from scratch

“SSE connection errors”

• SSE transport is no longer supported. The Tallyfy MCP server uses Streamable HTTP only
• Update Claude Desktop to the latest version, which defaults to Streamable HTTP

Best practices

1. Start with read-only tools - Use get_my_tasks, search_for_processes, and get_all_templates first to get familiar with the data before running write operations
2. Be specific - Name the template, process, or user explicitly. Claude performs best with complete context
3. Add human checkpoints - For write operations like creating automation rules, review Claude’s plan before confirming
4. Iterate on prompts - Review Claude’s outputs and refine your instructions over time

Cost and plan requirements

• Requires a paid Claude plan (Pro, Max, Team, or Enterprise)
• No additional Tallyfy charges for MCP usage
• MCP tool calls count toward your Anthropic usage limits

Related articles

Mcp Server > Using Tallyfy MCP server with Claude (text chat)

Claude Desktop provides the most mature MCP client experience for connecting to Tallyfy’s API through natural language and this guide covers setup via manual JSON configuration or one-click Desktop Extensions along with practical workflow examples like task management and process analysis and hybrid automation combining text-based MCP data queries with Claude Computer Use for visual UI tasks.

Integrations > MCP server

Tallyfy’s MCP Server lets you control workflows through plain English in any major AI platform like ChatGPT or Claude or Gemini or Copilot using the open Model Context Protocol standard to search tasks and launch processes and manage templates and set up automations without needing any API knowledge.

Byo Ai > ChatGPT integration

ChatGPT users on Plus or higher plans can connect to Tallyfy’s MCP server at https://mcp.tallyfy.com using OAuth 2.1 with PKCE to search and manage tasks and processes and templates and automations through plain language — with over 30 available tools covering everything from task creation to template health audits — though the text-based interface cannot replace Tallyfy’s visual workflow tracking or handle file uploads and

Integrations > BYO AI (Bring Your Own AI)

BYO AI lets you connect your existing AI subscriptions like ChatGPT or Claude directly into Tallyfy workflows through the MCP industry standard so your AI can read task context and complete steps and generate content and make decisions automatically inside running processes without any copy-pasting or app-switching.

Footnotes

1. Model Context Protocol - Anthropic’s open standard letting AI models call external tools and access data securely ↩

2. Proof Key for Code Exchange - prevents authorization code interception attacks during the OAuth flow ↩

Was this helpful?

YesNo