AI assistants
Is there an MCP server for freelance invoicing and client work?
Short answer
Yes. PaloWorks runs an MCP server that lets Claude, Cursor and other MCP clients create clients and projects, draft scopes, log time and revisions, and draft invoices in your workspace. Everything an assistant creates is a draft marked as made by your assistant: it never sends email, signs, charges or deletes anything. It is on the Pro and Studio plans.
Free for 1 client, 3 active projects. No card to start. Updated by PaloWorks.
What to look for
Real actions, not just reading
An assistant that can only read cannot save you the admin.
In PaloWorks
Twelve tools, including create_client, create_project, draft_scope, log_time, log_revision and draft_invoice.
Guardrails on money and clients
An assistant should never email a client or charge a card on its own.
In PaloWorks
Drafts only. No sending, signing, charging, marking paid or deleting, and no share links or client emails returned.
A clear record of what the assistant did
You need to know which records a person made and which an assistant made.
In PaloWorks
Assistant-created records carry a "Created by your assistant" badge in the app.
Ready-made workflows
Most people want outcomes, not tool calls.
In PaloWorks
Prompts such as scope_from_brief, scope_referee, bill_the_time and money_check.
Simple setup
Setup should take minutes.
In PaloWorks
Add the server URL as a connector and sign in, for an assistant that supports OAuth sign-in; or an API key from Settings and one config block for Claude Desktop, Claude Code or Cursor, shown on the developer page.
How it works in PaloWorks
Step 1
Add the server to your assistant
Add the server URL as a connector and sign in to PaloWorks when the assistant asks, or create an API key in Settings and copy the config for Claude Desktop, Claude Code or Cursor from the developer page.
Step 2
Choose a workspace and what it may do
On Pro or Studio, as an owner or admin. Signing in connects one workspace; a key belongs to the workspace it was made in.
Step 3
Ask in plain words
"Turn this client email into a project and a draft scope" or "Bill the time on the Atlas project."
Step 4
Review and send yourself
Open the draft in PaloWorks, check it, and send it. The assistant never sends.
When PaloWorks is the wrong pick
- If you want an assistant that sends invoices or charges clients by itself, PaloWorks will not do that, by design.
- An assistant needs to support either OAuth sign-in for MCP servers or a custom Authorization header; one that supports neither cannot connect.
Comparing tools? Read PaloWorks compared, including what the others are better at.
Questions people ask
- Which assistants work with it?
- Any MCP client that signs in with OAuth, as the MCP authorization spec describes, or can send an Authorization header with a key. The developer page shows setup for Claude Desktop, Claude Code and Cursor.
- Can the assistant send an invoice to my client?
- No. It can draft an invoice or estimate. Sending, signing, charging and marking paid stay with you in the app.
- Which plans include it?
- The API, and with it the MCP server by key or by sign-in, is on Pro and Studio. Pricing lists what each plan includes.
- Will my client's details be exposed to the assistant?
- The server never returns client email addresses, share links or payment ids. The assistant sees names and the work, which is what it needs to draft.