Use this file to discover all available pages before exploring further.
The Gryzzly app provides read/write access to the Gryzzly time-tracking SaaS through its v1 REST-RPC API. It can be used either as a Builder app (automations call Gryzzly instructions directly) or as a remote MCP server consumed by an AI Knowledge agent — covering customers, projects, tasks, declarations (time entries), leave periods, discounts, purchases, users, groups and tags.
Time Tracking
Declarations, leave periods and exports for payroll and invoicing
Project Structure
Customers, projects, tasks and metrics with budgets and contributors
Base URL of the Gryzzly API (default https://api.gryzzly.io/v1)
API Key
Gryzzly API key, stored as a workspace secret. Passed as Authorization: Bearer <token>
MCP Endpoint
Auto-populated on install — URL of the MCP endpoint for this instance
MCP API Key
Auto-populated on install — signed key used in the mcp-api-key header. Do not modify
MCP Endpoint and MCP API Key are generated automatically by the onInstall flow and are only needed to expose this instance as an MCP server (see the next tab).
Every instruction resolves credentials from the workspace configuration. All IDs are UUIDs returned by Gryzzly. Most list operations accept limit (max 1000) and offset for pagination.
The Gryzzly app ships with a built-in MCP server. Each app instance gets its own signed mcp-api-key that encodes the workspace ID and a credentials lookup URL — the Gryzzly API key itself is never passed through headers and is resolved server-side from the app configuration.
Use this flow to plug the Gryzzly MCP into an AI Knowledge agent that does not yet support the native MCP picker.
1
Install the Gryzzly app
Install and configure the app in the same workspace as your agent (see the Usage as App tab). Once configured, mcpEndpoint and mcpApiKey are auto-populated.
2
Copy the MCP credentials
Open the app instance config and copy the values of MCP Endpoint and MCP API Key.
3
Open your AI Knowledge project
Navigate to Advanced > Tools.
4
Add an MCP tool
Click Add and select the MCP tab.
5
Fill in the endpoint
Paste the MCP Endpoint URL copied from the app instance.
6
Add the auth header
In the Headers field, add the signed API key:
{ "mcp-api-key": "your-mcp-api-key"}
7
Save
The agent can now list and call Gryzzly tools through the MCP endpoint.
The signed mcp-api-key encodes the workspace ID and the getConfig webhook URL. The MCP server validates the signature using the central app secret and transparently fetches the Gryzzly API key and base URL from the installed app. Credentials are cached per tenant for 10 minutes.
budget_type ∈ none/detailed/global/time. hourly_rate_mode ∈ task/group/contributor. Supports parent_id for sub-tasks and is_container for parent tasks.
“Not configured” — The app instance has no API key. Generate one in Gryzzly > Administration > API Keys and paste it in the app configuration.“Invalid API key” (MCP) — The mcp-api-key header does not match the central app secret. Reinstall the app instance to regenerate a signed key.“Credentials lookup failed” — The MCP endpoint could not reach the getConfig webhook of the installed app. Verify that the app instance is still installed in the expected workspace.contributors rejected on public project — Set visibility: private or leave contributors empty.