No install? Use cloud.anythingmcp.com directly.
Sign in, install the Clockify in one click, paste the credentials, mint an MCP API key — done. No Docker, no git clone, no local server to run.
TL;DR
Manage Clockify (time tracking, projects, clients, tags, reports) from any AI agent. 10 tools, X-Api-Key auth.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Clockify, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Clockify + Gemini
Manage Clockify (time tracking, projects, clients, tags, reports) from any AI agent. 10 tools, X-Api-Key auth.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
CLOCKIFY_API_KEY
Step 1 — Get credentials
This connector wraps the Clockify REST API v1 (api.clockify.me/api/v1).
Setup:
- Sign in to https://clockify.me → bottom-left avatar → Preferences → Advanced → API → Generate API key.
- Set
CLOCKIFY_API_KEY.
Authentication: X-Api-Key: ${CLOCKIFY_API_KEY} on every request.
Workspace IDs: Clockify is workspace-scoped. Use clockify_get_user first — its response contains defaultWorkspace and activeWorkspace. List workspaces with clockify_list_workspaces.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
git clone https://github.com/HelpCode-ai/anythingmcp.git
cd anythingmcp && docker compose up -d
Step 3 — Add the connector in Gemini
Gemini CLI reads MCP servers from ~/.gemini/settings.json (or %APPDATA%\gemini\settings.json on Windows). Add:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp",
"headers": { "Authorization": "Bearer YOUR_MCP_API_KEY" }
}
}
}
- Get your MCP API key from AnythingMCP → Profile → MCP API Keys → New Key.
- Save the file and restart
gemini. - Run
/mcpinside the Gemini CLI —Clockifyshould be listed as available. - Vertex AI Studio: pass
https://cloud.anythingmcp.com/mcpto thetoolsarray of your request with the same Bearer header.
Available tools
| Tool | What it does |
|---|---|
clockify_get_user | Return the authenticated user: id, email, name, activeWorkspace, defaultWorkspace, profile picture URL |
clockify_list_workspaces | List workspaces the user belongs to |
clockify_list_clients | List clients in a workspace |
clockify_list_projects | List projects in a workspace |
clockify_list_tags | List tags in a workspace |
clockify_list_time_entries | List a user's time entries in a workspace |
clockify_start_time_entry | Start a new time entry |
clockify_stop_current_entry | Stop the currently running time entry for a user |
clockify_update_time_entry | Update a time entry's description, project, task, tags, billable status, or time range |
clockify_delete_time_entry | Permanently delete a time entry |
FAQ
Does Gemini 1.5 Pro or 2.x support MCP? Yes — Gemini CLI ≥ 0.4 and Vertex AI tools API both accept MCP httpUrl connectors with Bearer headers.
Next steps
Was this guide helpful?