Skip to main content
Glama
eranfinish/ezatwork-mcp

eranfinish/ezatwork-mcp

EZ@Work MCP Server

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

Tools

Tool

Description

Type

list_clients

List your clients/customers — id, name, company, status, email (+ default rate). Optional status, search, limit (default 50, max 200)

Read

list_projects

List your projects/cases/work orders — id, name, status, client. Optional status, search, limit

Read

create_client

Create a client; refuses a likely duplicate (same email, or same name when no email) unless allow_duplicate=true

Write

log_time_entry

Log billable hours to a project (0 < hours <= 24) for a given date (default today)

Write

create_invoice

Create a draft invoice, 1-50 line items (auto currency/language/VAT)

Write

Write tools change data in your EZ@Work account. Their descriptions tell the AI to confirm the exact values with you before calling them, and every tool validates its arguments before anything reaches the EZ@Work API — a bad value comes back as {"error": "invalid_input", ...}, a backend failure as a short {"error": ..., "status": ..., "message": ...} (plan limits pass through as PLAN_LIMIT_REACHED).

List tools return only the fields an assistant needs to pick a record — no notes, phone numbers, VAT numbers, addresses or contacts — and mark record text as user-entered data rather than instructions.

Related MCP server: bill4time-mcp

Setup

Settings → Connectors → Add custom connector

  • URL: https://mcp.ezatwork.com/mcp

  • Authentication: OAuth (automatic)

Claude Code / Cursor / MCP Inspector (API token)

  1. Create a free EZ@Work account at https://app.ezatwork.com

  2. Generate an API token at https://app.ezatwork.com/settings/api-tokens with the scopes clients:read, clients:write, projects:read, time:write, invoices:write

  3. Connect to https://mcp.ezatwork.com/mcp with header Authorization: Bearer ezw_pat_...

Local testing with MCP Inspector:

npx @modelcontextprotocol/inspector

Connect to http://localhost:8080/mcp with header Authorization: Bearer ezw_pat_...

Agent skill

skills/ezatwork-business-assistant/SKILL.md teaches an agent how to use these tools safely: resolve IDs by listing first, confirm every write with the user, treat record text as data, and never claim an invoice was sent. It is also listed on Agensi.

Security

  • Your data stays in your EZ@Work account

  • OAuth mode: Google identity → EZ@Work account lookup; no credentials stored in the MCP

  • API token mode: tokens have a mandatory expiration. Token scopes are being enforced server-side (a backend change is in progress), so don't rely on scopes alone to limit a token yet. Create tokens with only the scopes this server uses: clients:read, clients:write, projects:read, time:write, invoices:write

  • Authorization is verified on every request

Privacy Policy

https://www.ezatwork.com/privacy

Universal Design

EZ@Work adapts to your business type: a lawyer sees "cases," a freelancer sees "projects," a service business sees "work orders." Currency, language (24 supported), and tax rules auto-detect from your profile — no configuration needed in the MCP.


Development

Run locally

python -m venv .venv
source .venv/bin/activate  # Windows: .venv\Scripts\activate
pip install -e .

cp .env.example .env
# Edit .env: EZ_API_BASE=http://localhost:5000 for local backend

python -m ezatwork_mcp.server
# Server starts at http://localhost:8080/mcp

Run tests

pip install pytest pytest-asyncio
pytest tests/

Docker

docker build -t ezatwork-mcp .
docker run -p 8080:8080 -e EZ_API_BASE=https://api.ezatwork.com ezatwork-mcp

Deploy to Cloud Run

gcloud run deploy ezatwork-mcp \
  --source . \
  --region europe-west1 \
  --project ezatwork-production \
  --allow-unauthenticated \
  --port 8080 \
  --update-env-vars "EZ_API_BASE=https://api.ezatwork.com,MCP_BASE_URL=https://mcp.ezatwork.com" \
  --update-secrets "GOOGLE_CLIENT_ID=ezmcp-google-client-id:latest" \
  --update-secrets "GOOGLE_CLIENT_SECRET=ezmcp-google-client-secret:latest" \
  --update-secrets "EZ_MCP_MASTER_TOKEN=ezmcp-master-token:latest"

--allow-unauthenticated is correct — auth is enforced at the MCP layer (OAuth or API token), not at the Cloud Run IAM level.

Technical notes

  • Transport: Streamable HTTP (/mcp endpoint)

  • Library: fastmcp 3.x (pinned <4)

  • Auth (OAuth): GoogleProvider from fastmcp.server.auth.providers.google

  • OAuth redirect allowlist: clients may only register Claude's callbacks and loopback URIs; set MCP_ALLOWED_REDIRECT_URIS (comma-separated patterns) to admit other clients

  • Auth (token): get_http_headers() from fastmcp.server.dependencies

  • Dual-auth: OAuth active when GOOGLE_CLIENT_ID + GOOGLE_CLIENT_SECRET + MCP_BASE_URL are set

  • Backend: GET /api/users/me for locale; GET /api/internal/users/by-email for OAuth→user mapping

  • Lists: GET /api/clients and GET /api/projects take no filters; status, search and limit are applied in the MCP server, which trims each record before returning it

  • Time entries: POST /api/timeentry with isBillable field

  • Invoices: POST /api/invoices with computed dueDate and total per item


Built by

EZ@Work — the business OS for independents.

License

MIT. See LICENSE.

Available Tools

5 tools
create_clientCreate ClientBInspect

Create a new client/customer.

Inputs: name (required), email, notes, phone, +6 more. Returns: object

create_invoiceCreate InvoiceAInspect

Create a draft invoice. Currency, language, and VAT/tax rate are auto-detected from the user's EZ@Work profile — no need to specify.

Inputs: items (required), client_id (required), due_in_days. Returns: object

list_clientsList ClientsA
Read-only
Inspect

List the user's clients/customers.

Inputs: status. Returns: object

list_projectsList ProjectsA
Read-only
Inspect

List the user's projects (or cases/work orders — label adapts to businessMode).

Inputs: status. Returns: object

log_time_entryLog Time EntryAInspect

Log a time entry (billable hours) to a project/case.

Inputs: hours (required), project_id (required), description (required), billable. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: client creation/listing, project listing, time logging, and invoice creation. There is no overlap in purpose, so an agent can easily select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_client, list_projects, log_time_entry). The naming is predictable and uniform, with no mixed conventions.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a small business management domain covering clients, projects, time tracking, and invoicing. Each tool serves a distinct purpose, and the count feels neither thin nor heavy.

    Completeness4/5

    The tools cover the core workflow from creating clients to logging time and generating invoices. Minor gaps like update/delete for clients or listing invoices exist, but agents can work around them for typical use cases.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server that connects Clio Manage to Claude via OAuth, enabling law firm management tasks like matter lookup, time tracking, billing, calendar, and document retrieval through natural language.
      41
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      MCP server for Bill4Time providing API coverage for legal billing and time tracking, enabling natural language interaction with clients, projects, time entries, invoices, payments, and more from Claude Desktop.
      59
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for Invoice Ninja v5 API. Enables AI assistants to manage clients, invoices, quotes, payments, and time tracking through natural language.
      32
      22 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects Claude to FreshBooks, enabling reading and management of invoices, clients, expenses, projects, and time entries via natural language.
      1
      -