Ace Work Connector for Claude

Ace Work is a workflow intelligence platform. This connector lets Claude read your company's documented workflows, capture new ones through conversation, walk you through executing SOPs step by step, and log what actually happened so your documentation stays honest.

Server URL

https://work.aceworkflow.io/api/mcp

Claude runs a structured discovery interview about how a process really works, then files it into your Ace Work workspace as a reported workflow. No forms, no blank templates. You can also describe a process loosely and Claude will report it directly.

Any documented workflow has a step-by-step execution checklist. Claude walks you through it one step at a time and can use your other connected tools (email, calendar, CRM, accounting) to do the actual work in each step.

As you work, Claude records how long the run took, where you deviated from the documented process, friction points you hit, and general notes. All captures land as pending suggestions for human review in Ace Work. The connector never edits a documented workflow directly.

Browse your workflow library by keyword, department, company, and division.

Access tokens are short-lived (24 hours) and refreshed automatically with rotating refresh tokens. Tokens are stored hashed on our side and every connection can be revoked at any time from the Connect Claude page inside Ace Work.

Regular users are scoped to their own company automatically — there is nothing to select. Ace Workflow staff who administer multiple client workspaces choose an active company in conversation before workspace tools work (Claude will prompt for this).

Every read is scoped by up to three levels:

1. Company

The workspace. Single-company accounts are scoped to their own company automatically and cannot change it. Ace Workflow staff select a client company in conversation.

2. Division (optional)

Narrows workflow reads to one division of the active company, for example a beta group or a business unit. Division selection is a staff-only tool; regular users always read at their company scope.

3. Department

Workflows are organized under departments (Sales, Operations, Finance, and so on).

Company and division selections persist for the connection until changed.

The connector exposes 18 tools. The six scope-selection tools are visible only to Ace Workflow staff accounts that administer multiple client workspaces — regular single-company users never see them in their tool list, because their scope is fixed to their own company.

list_departments

Lists the active company's departments.

my_workflows

Lists workflows you've personally reported plus your company's documented SOPs. Each entry is marked documented (full SOP with steps) or reported (captured but not yet documented into steps).

search_workflows

Keyword search across documented workflow titles and descriptions. Reported workflows are not searched here; use my_workflows.

get_workflow

Returns one workflow in full. Documented workflows include description, department, tools, and ordered steps. Reported workflows return their reported detail.

get_workflow_checklist

Returns a step-by-step execution checklist for a documented workflow, formatted for Claude to guide you through the work.

get_discovery_agenda

Returns the structured discovery interview agenda so Claude can interview you about an undocumented process.

submit_discovery_interview

Submits a completed or partially completed discovery interview for processing. Extracted workflows are saved as drafts pending human review — nothing is auto-confirmed.

report_workflow

Creates a new reported workflow from your description. It enters the workspace as reported and awaits documentation.

log_time_taken

Records the actual minutes a workflow run took, for review against estimates. 1 to 1,440 minutes, with optional context.

log_deviation

Records that the real process differed from the documented one (extra step, skipped step, different tool, different order). Lands as a pending suggestion, never a direct edit.

flag_pain_point

Records a friction point or bottleneck in your own words, as a pending signal for the operations team.

add_note

Attaches general notes or tribal knowledge about how work really happens, optionally tied to a workflow, for human review.

The connector reads:

Your accessible company list, departments, divisions, and workflow content (titles, descriptions, steps, tools, departments) within the active scope. Every read is tenant-scoped to the company bound to your connection — scope comes from the server-side token, never from anything Claude sends.

The connector writes:

Reported workflows, discovery interview submissions, time logs, deviation records, pain point flags, and notes. All writes are additive capture rows queued for human review inside Ace Work; nothing modifies or deletes documented SOPs.

The connector never accesses:

Billing or payment data, user credentials or passwords, email content, or data belonging to other companies in Ace Work.

Data you capture through Claude is stored in your Ace Work workspace under the active company, in the same PostgreSQL database that holds the rest of your workspace data. Every tool call is logged to an append-only audit trail visible to your administrators.

Conversation content is only sent to Ace Work when a tool is called, and only the tool's parameters (for example, the note text or the deviation description). Claude conversations are otherwise not shared with Ace Workflow.

If Claude reports that expected tools aren't available, the connection's tool list is stale. The server nudges Claude to refresh automatically, but if it persists, disconnect and reconnect the Ace Work connector in Claude's Settings → Connectors, which refreshes it.

Reconnect the connector to refresh, then confirm in the Ace Work admin that your account has access to it.