MCP example workflows

Use safe prompts to review readiness, payroll results, exceptions, evidence, and confirmed operator actions through PayCanvas MCP.

These workflows use the public payroll-operator connector. Ask in business terms; the connector resolves internal identifiers and keeps them out of the conversation where possible.

Prerequisites

  • A connected PayCanvas operator MCP server.
  • Access to the account and period you want to review.
  • The optional permission for any workflow that can change PayCanvas data.

Check workspace readiness

Prompt:

Show my PayCanvas payroll accounts, select Acme Tours, and explain what is blocking the next payroll run. Do not change anything.

Expected result: the assistant checks the accounts allowed by your access, reports safe blocker codes, and suggests only supported next steps.

Review the latest calculated run

Prompt:

Review the latest PayCanvas period. Summarize the calculation status, assigned payroll, held money, unresolved questions, balancing checks, adjustments, and whether the result is provisional or final.

Expected result: the assistant finds the latest period, reads its saved result, and does not confuse a final calculation with approval or payment.

Explain one amount

Prompt:

Explain Jordan's tip amount in the latest run using the stored rule and sanitized source evidence. Do not show raw reports or private provider data.

Expected result: the assistant explains the matching payroll line using only safe source descriptions and references.

Review an unresolved item

Prompt:

List the open pay-affecting items in the latest run, explain the first one, and show only the resolution choices PayCanvas currently offers. Do not apply anything.

Expected result: the assistant presents the factual question, the held amount, and only the choices PayCanvas currently allows. It does not invent an answer.

Apply an offered resolution

Prompt:

Preview the selected offered choice for that item. Quote the exact effect and wait for my explicit confirmation before applying it.

Expected result: when the connection has resolution permission and you are an authorized payroll operator, the assistant previews the exact choice and waits. After confirmation, PayCanvas recalculates from the same locked source data instead of downloading provider data again.

Start source collection or calculation

Prompt:

Preview source collection for August 1 through August 14. Tell me the exact effect and blockers, and do not start until I explicitly confirm.

Or:

Preview calculation for the source-complete August 1–14 period. Show which locked source snapshot and payroll settings will be used, then wait for confirmation.

Expected result: no work starts during preview. A confirmed action still requires the matching optional permission, authorized payroll-operator access, and a preview that still matches the current payroll state. PayCanvas also protects against accidentally submitting the same request twice.

Expected results

The connector reads only the selected payroll account and fields allowed by your role. Read workflows make no changes. Workflows that can change data show the exact effect, wait for confirmation, and stop safely when the connection permission, user role, or payroll state is insufficient.

Troubleshooting

  • The assistant asks for an internal ID: ask it to find the payroll account or period with PayCanvas instead.
  • A change is unavailable: reconnect with the optional permission only if the action is required and authorized.
  • The agent proposes a rate, mapping, or arbitrary amount: stop. Those are outside the operator connector's offered-choice boundary.
  • Results contain private raw data: stop the workflow and contact support; the implemented connector is designed to return sanitized evidence.
SOLVING THIS WITH CHATGPT?

Share this article URL and describe what happened.

Include the step you are on, what you expected, and a safe error code. Do not share employee pay, raw reports, credentials, MFA codes, or access tokens.