Overview
Drum has a remote MCP (Model Context Protocol) server. It lets AI assistants such as Claude, ChatGPT and Cursor, and agents you build yourself, read and change Drum data for one of your users. Ask “log two hours on the drainage design for 21 Drum St” or “which opportunities close this month?”, and the assistant does it in Drum.
| Server URL | https://app.getdrum.com/api/v1/mcp |
| Transport | Streamable HTTP. Hosted by Drum, nothing to install |
| Sign-in | Sign in with Drum (OAuth) for hosted clients, or an API token |
| Acts as | One Drum user, in one account, with that user’s permissions |
| Tools | 80, in eight toolsets. Each connection gets only the toolsets you select |
Get started
- Connect a client. For Claude, ChatGPT and other hosted clients, use Sign in with Drum. For Claude Code, Cursor, VS Code and Codex, use an API token.
- Choose toolsets. Start with My work, and add others as you need them.
- Ask. See Example prompts for ideas.
New to it? Follow the tutorial Connect Claude and log your first time entry. Building on the server? Start with Make your first MCP call.
What you can do
| Toolset | What an assistant can do |
|---|---|
| My work | Find projects and tasks, log and correct time, record costs and receipts, submit expense claims, update tasks, add notes |
| Sales | Work the pipeline, build opportunities and proposal budgets, convert won work to projects, read the sales reports |
| Clients | Find, add and update companies and contacts, link contacts to work, merge duplicates |
| Proposals | Write proposal documents, send them, and read the clients’ answers |
| Insights | Read the overview, revenue and receivables reports |
| Setup, Templates, Proposal templates | Set up an account’s catalogs and templates, where Drum has turned this on |
Supported clients
| Client | Connect with |
|---|---|
| Claude (claude.ai, Desktop and mobile) | Sign in with Drum |
| ChatGPT | Sign in with Drum |
| Grok, Cursor hosted agents, Microsoft Copilot Studio | Sign in with Drum |
| Claude Code, Cursor desktop, VS Code, OpenAI Codex | API token |
| Anthropic API, OpenAI Responses API, MCP SDKs | API token |
See Supported clients for the details.
Safe by design
- An assistant acts as you. It sees and does only what your Drum role allows, and its changes are recorded under your name.
- Tools that send email, delete data or cannot be undone are marked destructive, and the assistant is told to ask you first.
- You can see and revoke every connection under Profile, then Connected Agents.
Read Keeping AI access safe before you connect an assistant to anything sensitive.
Reference
| Page | Covers |
|---|---|
| Server and protocol | The endpoint, protocol versions, methods, instructions and tool annotations |
| Authentication and permissions | Sign in with Drum, API tokens, scopes, and the checks behind every tool |
| Toolsets | The eight toolsets, shared tools, and how the selection works |
| Supported clients | Which clients connect, and how |
| Results, errors and limits | Result shapes, pages, idempotency keys, error codes and rate limits |
| Example prompts | What to ask, by toolset |
| Tools | Search, delete and restore, My work, Sales, Clients, Proposals, Insights, Setup, Templates, Proposal templates |
Tutorials, how-to guides and explanation
- Tutorials: Connect Claude and log your first time entry, Make your first MCP call
- How-to: Connect a hosted AI client, Connect a client with an API token, Choose toolsets, Manage and revoke connections, Give an assistant its own Drum user, Log time and costs with an assistant, Build an agent on the Drum MCP server, Troubleshoot an MCP connection
- Explanation: How AI assistants work with Drum, Keeping AI access safe, MCP or the REST API?