EZ@Work MCP Server

Manage clients, projects, time, and invoices in EZ@Work — business management for freelancers.

Remote serverstreamable-httpPython

What is the EZ@Work MCP server?

Manage clients, projects, time, and invoices in EZ@Work — business management for freelancers. Exposed over MCP by the ez@work mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Connect EZ@Work — all-in-one business management for freelancers, lawyers, agencies, and service businesses — to Claude, Gemini, Cursor, and any MCP-compatible AI.

Its toolset

Everything the assistant can do here goes through one of these:

  • list_clients — List your clients/customers
  • list_projects — List your projects/cases/work orders
  • log_time_entry — Log billable hours to a project
  • create_invoice — Create a draft invoice (auto currency/language/VAT)

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 4 environment variables: MCP_BASE_URL, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, EZ_MCP_MASTER_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. EZ@Work's toolset — list_clients, list_projects, log_time_entry and 1 more — is a fair guide to whether it matches your workflow. It is maintained by eranfinish; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the ez@work mcp server does with a few real requests.

Available tools

ToolWhat it does
list_clientsList your clients/customers
list_projectsList your projects/cases/work orders
log_time_entryLog billable hours to a project
create_invoiceCreate a draft invoice (auto currency/language/VAT)

How to install the EZ@Work MCP server

{
  "mcpServers": {
    "ezatwork": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "MCP_BASE_URL": "your-value",
        "GOOGLE_CLIENT_ID": "your-value",
        "GOOGLE_CLIENT_SECRET": "your-value",
        "EZ_MCP_MASTER_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MCP_BASE_URLEndpoint or connection string the server talks to.Yes
GOOGLE_CLIENT_IDConfiguration value read at startup.Optional
GOOGLE_CLIENT_SECRETCredential the server authenticates with.Yes
EZ_MCP_MASTER_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use EZ@Work to list clients.
  • Use EZ@Work to list projects.
  • Use EZ@Work to log time entry.

Frequently asked questions

It connects EZ@Work to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (list_clients, list_projects, log_time_entry, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with EZ@Work directly.