eranfinish/ezatwork-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EZ_API_BASE | No | URL of the EZ@Work backend API (default http://localhost:5000 for local development, https://api.ezatwork.com for production) | http://localhost:5000 |
| MCP_BASE_URL | No | Base URL for the MCP server (required for OAuth; e.g., https://mcp.ezatwork.com for production) | |
| GOOGLE_CLIENT_ID | No | Google OAuth client ID (required for OAuth mode) | |
| EZ_MCP_MASTER_TOKEN | No | Master token for internal API authentication (optional, for server-to-server communication) | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret (required for OAuth mode) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clientsA | List the user's clients/customers. |
| create_clientB | Create a new client/customer. |
| list_projectsA | List the user's projects (or cases/work orders — label adapts to businessMode). |
| log_time_entryA | Log a time entry (billable hours) to a project/case. |
| create_invoiceA | Create a draft invoice. Currency, language, and VAT/tax rate are auto-detected from the user's EZ@Work profile — no need to specify. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.