TaskRay MCP: Tool Reference Overview

When someone in your org connects an AI assistant such as Claude, ChatGPT or Copilot to TaskRay MCP, the assistant works through a set of tools, such as reading a Project or creating a Task. The TaskRay MCP Tool Reference covers what those tools let a user's assistant do in your org, and which parts of the setup are yours to manage.

Throughout this reference, "the user" is the person whose TaskRay MCP connection makes the request, and "the assistant" is the AI they connected. Every tool runs with the user's own Salesforce permissions, so the access you set up decides what their assistant can reach. If you're new to TaskRay MCP, start with Getting Started with TaskRay MCP and TaskRay MCP: Administration Installation & Setup.

In this article:

  • How changes are approved
  • What decides which tools a user gets
  • Good to know
  • Frequently asked questions
  • Articles in this reference

How Changes Are Approved

Risk tier What the assistant is doing When it runs
Read-only Reading data Straight away
Reversible Creating or updating one record Straight away
Destructive Deleting a record, sometimes with the records that belong to it After the user approves it
Bulk Creating or updating up to 200 records in one request After the user approves it
Elevated Cloning a Project, stitching template content into a Project, importing a template, or archiving or unarchiving a template After the user approves it

A change that waits isn't made until the user approves it, as described in TaskRay MCP Tool Reference: Approvals for Delete, Bulk and Elevated Tools.

What Decides Which Tools a User Gets

  • A TaskRay license. A user without one gets no TaskRay tools.
  • Object permissions. A user who can read Time Entries but can't delete them won't get the tool that deletes a Time Entry.
  • The TaskRay - Admin Access or TaskRay - Template Manager Access permission set, to create, activate, deactivate, archive or unarchive a template.
  • Access to TaskRay's cloning, stitching and Template Migration features. Template export and import also need TaskRay Premium or the Template Migration add-on, as described in TaskRay MCP Requirements and Licensing.

Record sharing and field-level security still apply to every request. Assistants read and set your org's own custom fields only after you've exposed them, as described in TaskRay MCP Tool Reference: What Assistants Can Find and Change Safely.

Good to Know

  • When your org and its sandboxes together reach 80% of their monthly TaskRay MCP tool-call allowance, and again at 100%, the assistant shows the user a message. Requests keep working.

Frequently Asked Questions

Q. I gave a user a new permission set, but their assistant still can't use the tool. Why?

Great question! The tools a user gets are worked out when they connect. Ask the user to reconnect, and if nothing has changed, wait a few minutes and reconnect again, because TaskRay MCP can take up to 15 minutes to pick up a permission change.

Articles in This Reference

Have a question this reference doesn't answer? Not to worry, our Support Team is ready to help! Contact TaskRay Support with what the user asked their assistant to do, the exact error text, and whether the org is production or sandbox.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request