Each Connected Agent connection and each API token stores the MCP toolsets you selected. The MCP endpoint only serves tools from that selection. Your Drum role and permissions still decide what each tool can see and do.

A toolset is a named group of MCP tools for a type of work. Screens show only the toolsets that give you tools in that account.

Toolsets that currently offer tools include:

When account settings through the API is available for your account, the screens can also offer:

Those three appear only when your account has that API access. If you do not see them and need them, contact Drum. The Settings screens in Drum itself use the same setup behaviour for everyone with the usual permissions; they are not gated by that API access.

Other toolset names exist in Drum for later work. They are not offered on the screens until they have tools of their own.

The default selection is My work.

When an AI client uses Sign in with Drum:

When you switch account on the consent screen, the toolsets and counts update for that account. My work stays selected unless you change it.

Changing toolsets does not revoke the connection. The client picks up the new tools the next time it lists them. Some clients only list tools when they connect, so reconnect or restart the client if the tools do not change.

Until you save a selection on an existing connection, Drum shows: "This connection now uses My work. Select more toolsets for more tools."

Until you save a selection on an existing token, Drum shows: "This token now uses My work. Select more toolsets for more tools."

Account-scoped API tokens authenticate the MCP endpoint the same way they authenticate the REST API. See Drum API authentication, permissions and rate limits.

The MCP endpoint /api/v1/mcp only serves tools in the stored selection. If a client calls a tool you can use in Drum but that is not in the selected toolsets, Drum returns a tool error with reason tool_not_selected.

The message names the toolsets that include that tool. Add one of those toolsets on Connected Agents or on the API token, then ask the client to list tools again.

This is separate from a permission failure. If your role cannot use the tool, Drum answers not_authorized whether the toolset is selected or not.

delete_record and restore_record only offer the kinds that belong to the toolsets you selected and that your role can use. My work covers kind tracked_time on delete_record only (permanent delete). Setup, Templates and Proposal templates add their own delete and restore kinds when those toolsets are available and selected. Sales does not include either tool.

If a kind you need is not offered, add the toolset that includes it, then ask the client to list tools again. Calling a kind that lives in a toolset you did not select answers like a tool that was not selected.

Connections and tokens created before toolset selection keep My work until you expand them. For a full administrator that means fewer tools than the old all-tools list until you select more toolsets (for example Sales or Insights).

When the selection is more than about 30 tools, Drum shows a warning: the agent can choose the wrong tool more often with more than 30 tools, mainly in claude.ai and ChatGPT. You can still save the selection.

A tool that appears in more than one selected toolset counts once in the total.

When the Insights toolset is selected, get_revenue_report and get_overview_report use the same Net revenue and unpaid-balance rules as the Insights dashboard with no filter.

Default MCP month windows use the full calendar month. The dashboard current month for actuals runs through yesterday. See How Insights Net revenue and outstanding amounts are calculated.