Connect Claude, ChatGPT, and Codex to your Growee data
Growee runs an MCP server for your tenant, so Claude, Claude Code, ChatGPT, and Codex read your HR and CRM data and act on it, with your permissions.
Checking your pipeline in Growee, sorted by fit score.
Marta Iversen is your strongest fit: booked for a meeting, €64,000 expected.
This one writes data. You’ve granted campaigns:write.
It’s ready to review in Growee before anything sends.
Set up in three steps
Connect your assistant to Growee in about two minutes, the same flow for every MCP client. HR software integrations usually mean a project; this one is a paste and a sign-in.
Copy your server URL
In Settings, open AI Agent Integration and copy the MCP Server URL for your tenant.
Add the connector
Paste it into your assistant. In Claude Code, that's one command:
claude mcp add growee --scope user --transport http "https://{tenant}.api.growee.net/mcp/restify"Sign in with your Growee account
Run claude mcp login growee and approve the browser sign-in. The assistant now acts with your role.
One page connects every assistant
Copy a URL, add the connector, sign in. The same three steps work for every AI client your team uses.
Every AI client, one settings page
Open Settings, find AI Agent Integration, and you get a provider card for each assistant your team uses.
- One place to manage access: Claude, ChatGPT, and Codex each get a card with the exact steps to connect.
- Copy your server URL: grab the MCP Server URL for your tenant and paste it into any client that speaks MCP.
- Static tokens when you need them: for scripts and headless clients, issue a token with a per-tool allowlist instead of a full OAuth sign-in.
Paste one command, sign in
Claude Code connects with a single command and a browser sign-in (no config files to hand-edit).
- Add the connector: run
claude mcp add groweewith your server URL and the tools register automatically. - Sign in with Growee:
claude mcp login groweeopens an OAuth flow, so the assistant acts as you, with your role. - Start asking: the moment it's connected, Claude can read your pipeline and act on it.
Same data, a different assistant
ChatGPT reaches the same Growee data through its own connector card. Nothing about your setup changes.
- Add a custom connector: paste the MCP Server URL into ChatGPT's connector dialog and sign in with Growee.
- One server, many clients: Claude, ChatGPT, and Codex all read the same leads, campaigns, and reports.
- Consistent answers: every assistant works from your live tenant data, so the answer doesn't depend on which one you open.
One connection, your whole workspace
MCP (Model Context Protocol) is the open standard that lets AI assistants read and act on data from outside apps. Instead of a custom integration per tool, an assistant connects once and reaches everything the server exposes.
Growee's server exposes more than 70 areas of your workspace (leads, campaigns, people, time off, hours, documents, invoices, and more), each with permission-based read and write. It's an MCP server for HR and CRM data, so the assistant you already use can work across the same records your team does.
What your AI can do once connected
Ask pipeline questions
Ask which leads fit best or where deals are stalling, and get an answer from live data (no dashboard to open).
Create leads and campaigns
Have your assistant add a lead straight into your pipeline, or draft a campaign. Campaigns are created in draft by default, and drip automation only starts sending once you activate them.
Check who's off
Ask who has approved time off this month and get the list, scoped to what your Growee role is allowed to see.
Pull hours and reports
Ask for logged hours or a time report on a project and read the numbers back in the chat, straight from your timesheets.
Draft documents from your data
Ask for a document generated from a Growee template, filled in with real record data and filed where it belongs.
Automate from any MCP client
Connect Claude, ChatGPT, or Codex. The same server answers them all, so you pick whichever assistant you already use.
The agent surface is a distribution channel
A system your team's assistant cannot reach is not in the workflow. Amadeus, Cisco and HiBob each said so out loud, on the record.
Travel content, inside the coding tool
The travel-tech company announced a toolkit that puts its documentation, authentication and travel content into Claude Code, plus a proposed Claude Cowork plugin. Both are pre-general-availability, with a waitlist open.
Source: Skift, September 3, 2026One assistant for 90,000 staff
Cisco's own post says its MyAgent super-agent is "now rolling out to 90,000 employees", moving work "beyond chat and into supervised autonomous execution" on its internal AI platform.
Source: Cisco blog, August 27, 2026HR repositioned around intelligence
Announcing a $166M investment led by Salesforce, the HR platform described the round as a step in its evolution into "an organizational intelligence layer for modern businesses" (its phrase, in its own announcement).
Source: HiBob newsroom, September 1, 2026Growee's answer is one MCP connection: an assistant reaches your people, leave, documents, hours and leads across more than 70 areas, and every call runs as your own Growee user, with your role's permissions. It is on the free plan, metered at 1,000 successful MCP tool calls a month, with the meter off on any paid plan. HiBob ships an MCP server too (we compare the two). Several other HR systems ship one as well: here is which HR vendors ship MCP servers, compared.
Your permissions, enforced on every call
Every call runs inside your tenant and as your Growee user: reads return what your role can already see, and writes run the same permission checks Growee already applies.
The security posture behind that, question by question, is on the MCP server security page.
Bounded by your role
Sign in with OAuth and the assistant acts as your Growee user. It reads the records your role can already see, and its writes carry the same checks you have in the app.
Per-token allowlists
For scripts and headless clients, static tokens carry an explicit per-tool allowlist, so a token does only what you granted it.
Nothing escapes the boundary
Every call runs inside the same tenant scoping Growee already applies, so nothing leaves your permission structure.
Frequently asked questions
What is an MCP server?
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to the apps where your data lives. An MCP server is the endpoint that exposes that data. Growee runs one for your tenant, so an assistant like Claude or ChatGPT can reach your HR and CRM records over a single connection instead of a one-off custom integration.
Which AI assistants work with Growee?
Claude, Claude Code, ChatGPT, Codex, and any other client that speaks MCP. You paste the same server URL into each one, so a new assistant is a two-minute setup rather than a new build.
Can the AI change data or only read it?
Both. It can read your records and it can create or update them: add a lead, draft a campaign, generate a document. Every call runs as your Growee user inside your tenant: reads return the records your role can already see in the app, writes run the same permission checks the app applies, and a static token is limited to the tools you put on its allowlist.
Can I connect ChatGPT to my database directly?
Effectively, yes (without handing over raw database access). ChatGPT talks to the Growee MCP server, which enforces your permissions on every call. It reaches your leads, hours, and documents through the same rules Growee already applies, not through a direct connection to the underlying database.
Is the MCP integration included in my plan?
Yes, every plan includes MCP access, including the free one. On the free plan, calls are metered at 1,000 successful tool calls a month; on any paid Growee plan (a paid CRM tier or any other paid subscription), the meter comes off. The CRM itself is free to start (up to 100 leads and one CRM seat), so if you have a Growee login, you can connect an assistant from the AI Agent Integration settings today.
Is Growee an "organizational intelligence layer"?
That is not our phrase, and we would rather describe what ships. Growee runs one MCP server for your tenant, exposing more than 70 areas of the product: people, leave, hours, documents, invoices, leads, campaigns and more. Every call runs as your own Growee user inside your tenant: reads return what your role can already see, writes run the same permission checks the app applies, and a static token is limited to the tools on its allowlist. Claude, Claude Code, ChatGPT, Codex or any other client that speaks MCP can connect to the same server URL. On the free plan that is metered at 1,000 successful tool calls a month, with the meter off on any paid plan, and the CRM is free to start (up to 100 leads and one CRM seat).
Connect your assistant to Growee today
Copy your server URL, add the connector, and start asking (no new tool to learn).