Browse all guides

MCP & AI Tools

Growee ships a first-class Model Context Protocol (MCP) server. Instead of writing REST glue code, you can point Claude, ChatGPT, Codex or any MCP-capable agent at your workspace and let it read and manage data in plain language - governed by the same permissions as your users.

The MCP server

Every workspace has its own server URL:

https://<your-company>.growee.net/mcp/restify

You can copy the exact URL from Configurations → Integrations → AI Agent Integration in Growee - the same page has setup cards with click-by-click instructions for ChatGPT (Browser), Codex (Desktop/CLI) and Claude (Browser/Desktop/CLI).

The server exposes the whole API surface through four discovery tools:

Tool Purpose
discover-repositories List the resources available to the connected user.
get-repository-operations List the operations of one resource (list, create, update, actions, getters).
get-operation-details Fetch the full input schema of one operation.
execute-operation Run the operation.

This keeps the tool list small for the agent while still covering employees, timesheets, holidays, projects, CRM and everything else - the agent discovers what it needs, when it needs it.

Connect Claude (browser)

  1. In Claude, go to Settings → Connectors.
  2. Click Add → Add custom connector.
  3. Name it “Growee” and paste your MCP server URL. Leave advanced settings empty.
  4. Save, then sign in with your Growee account to authorize (OAuth).

Then enable the Growee tools in any chat and ask things like “log 2 hours on the Website Redesign project for today” or “who is on holiday next week?”.

Connect Claude Code (CLI)

claude mcp add growee --transport http https://<your-company>.growee.net/mcp/restify

Claude Code walks you through the OAuth sign-in on first use. The AI Agent Integration page in Growee also offers a ready-made command with your exact URL.

Headless clients: MCP tokens

Interactive agents sign in with your Growee account. For scripts, CI jobs or headless agents that cannot complete OAuth, create an MCP client token instead:

  1. Open Configurations → Integrations → AI Agent Integration → MCP Client Tokens.
  2. Create a token and select which MCP tools it may call (or all of them).
  3. Send it as a bearer token when connecting to the MCP URL:
claude mcp add growee --transport http \
  https://<your-company>.growee.net/mcp/restify \
  --header "Authorization: Bearer <mcp-token>"

MCP tokens and REST API keys are separate credentials. An API key cannot call MCP tools, and an MCP token is not meant for REST endpoints. Scope each one to its job.

Permissions

MCP never widens access. Every operation runs under the connected user’s roles and permissions - an agent can only see and change what that user already can in the app. Actions performed by agents are attributed to the connecting user.

When to use MCP vs the REST API

Use case Pick
AI assistant working with workspace data conversationally MCP
Deterministic integration, sync jobs, webhooks-style polling REST API
Internal tool with its own UI REST API
Agent that occasionally needs live Growee context MCP

Questions about the API? Contact support or email support@growee.net.