easyJOB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EASYJOB_PASSWORD | No | The easyJOB password (used for password grant token lookup). | |
| EASYJOB_USERNAME | No | The easyJOB login name (used for password grant token lookup & user ID resolution). | |
| EASYJOB_API_TOKEN | No | Optional. A static, long-lived bearer token (bypasses automatic auth flows). | |
| EASYJOB_CLIENT_ID | No | OAuth Client ID (if using client credentials flow or required for password flow). | |
| EASYJOB_TOKEN_URL | No | Optional. Custom OAuth Token URL (defaults to ${EASYJOB_API_BASE_URL}/oauth/token). | |
| EASYJOB_API_BASE_URL | Yes | Required. The absolute URL to the easyJOB app (e.g., https://easy4.because-software.com/drid/app). | |
| EASYJOB_CLIENT_SECRET | No | OAuth Client Secret (if using client credentials flow). |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_idA | Get the internal easyJOB User ID for the configured user (EASYJOB_USERNAME). The User ID is required to track hours. |
| search_jobsA | Search for jobs in easyJOB by Name, ShortName, or JobNo. Returns matching jobs with their IDs. Always run this to find the correct JobId before logging time. |
| track_timeA | Log working hours on a specific job in easyJOB. Creates a TimeRecording entry for the configured user. Supports duration (amount) OR start/end times (from_time/to_time). |
| query_entitiesB | Execute a generic FetchsonQuery against any easyJOB entity. Allows filtering and custom selections on User, Job, TimeRecording, Task, etc. |
| create_or_update_entityB | Generic tool to create or update any entity (e.g. TimeRecording, Task) in easyJOB. |
| delete_entityB | Delete an entity in easyJOB by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| import-hours | Guides the AI agent on how to dry-run map, verify, and import a batch of working hours (timesheet) into easyJOB, supporting start/end time parsing. |
| weekly-summary | Retrieve, review, and aggregate your logged hours for the current week, comparing it to target working hours. |
| project-budget-status | Query and inspect budgeted hours vs actual logged hours (burn rate) for a specific Job in easyJOB. |
| daily-standup-helper | Generates a clean bulleted status report of your activities based on logged easyJOB entries for today (or yesterday). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| easyJOB MCP Integration Guide | The complete instructions and safety protocols on how to securely log hours and resolve ambiguities. |
| easyJOB REST API Query Guide | Documentation on FetchsonQuery syntax, operators, and common entities (User, Job, Activity, TimeRecording). |
| Current User Profile Details | Dynamically retrieves the profile and database record of the currently authenticated user. |
| Today's Time Recordings | Live query of all hours logged by the current user today. |
| This Week's Time Recordings | Live query of all hours logged by the current user during the current week (Monday to Sunday). |
| Active Jobs List | Live query of up to 50 active, open jobs in easyJOB where time recording is permitted. |
TDQS
Scored across 6 tools
Most tools have distinct purposes (track_time vs. generic CRUD, search_jobs, etc.), but the generic create_or_update_entity could cause slight confusion when a specialized tool like track_time exists for similar entities.
All tool names follow a consistent verb_noun pattern using lowercase snake_case, e.g., create_or_update_entity, delete_entity, query_entities, search_jobs, track_time.
Six tools cover the core domain (job management, time tracking) without being excessive or insufficient; each tool serves a clear purpose.
Generic CRUD tools cover basic operations but lack specialized tools for updating jobs or managing users; the set works but has notable gaps for a full workflow.