Multi-step agents
Run autonomous workflows on GroWrk lifecycle data. The agent runs, the work gets done.
"Every Monday, audit devices approaching end-of-life and email a summary to IT ops."
The AI operating layer for global IT lifecycle
IT teams already run AI assistants — yet still log into app after app to check one order, device, or employee. GroWrk MCP is the first connector that brings live lifecycle data and real actions straight into Claude, ChatGPT, and Cursor.
AI tools
Custom agents
GroWrk MCP
GroWrk lifecycle data
Get connected · For developers
Authenticated HTTP MCP over OAuth — no API keys to provision or rotate. Add the connector the same way you already add one in Claude or ChatGPT.
Choose your client — Claude, Claude Code, Cursor, ChatGPT, or any MCP-compatible client.
Open claude.ai → Settings → Connectors → Add custom connector. Paste the URL and sign in with GroWrk.
Name GroWrk MCP
URL https://ai.growrk.com/mcp
Add the connector from your terminal with the Claude Code CLI.
claude mcp add growrk --transport http https://ai.growrk.com/mcp
Open Cursor → Settings → MCP → Add new MCP server, then authenticate with GroWrk.
{
"mcpServers": {
"growrk": { "url": "https://ai.growrk.com/mcp" }
}
}
In ChatGPT → Settings → Connectors → Add custom connector, paste the URL and sign in with GroWrk.
Name GroWrk MCP
URL https://ai.growrk.com/mcp
Point any MCP-compatible client at the authenticated HTTP endpoint over OAuth.
transport: http
endpoint: https://ai.growrk.com/mcp
auth: oauth
Authenticate with GroWrk. Your role determines the tools you get.
Beyond visibility
Use GroWrk MCP to power audits, onboarding checks, lifecycle reports, and cross-system workflows across the tools you already use — Slack, Jira, Workday, and your own AI agents.
Run autonomous workflows on GroWrk lifecycle data. The agent runs, the work gets done.
"Every Monday, audit devices approaching end-of-life and email a summary to IT ops."
Combine GroWrk lifecycle data with Slack, Jira, Workday, or anything else your AI tool can reach.
"Cross-reference our GroWrk devices with our Jira tickets and Workday hires to see which new employees still need a laptop."
The cockpit
One question, and GroWrk surfaces exactly what your team needs to act on — with vendor, warehouse, logistics, and partner coordination handled behind the scenes.
| Status | Order type | Country | Action needed | Action suggested |
|---|---|---|---|---|
| Input needed | New hire laptop | 🇩🇪 Germany | Waiting on employee address | Add missing address |
| Approval needed | Replacement device | 🇧🇷 Brazil | Awaiting device selection approval | Approve replacement model |
| Response needed | Retrieval | 🇬🇧 United Kingdom | Employee has not scheduled pickup | Send employee reminder |
Available today
Every capability is live and read-scoped to the signed-in user.
See who's onboarding, who's missing a device, and where every employee's device is right now.
Every order — assigned, in transit, ready for dispatch — across every region.
Know which milestones are on track and which ones need your input before they slip.
Missing addresses, pending approvals, employee responses — surfaced clearly.
Each item shows what your team needs to do and the next milestone after that.
Assigned, in storage, ready to redeploy, or eligible for end-of-life — at a glance.
Procure → End-of-life
Seven stages, one continuously refreshed signal. Hover any stage to see what AI can read there.
AI-readable status across every stage · signals refresh continuously
Security & permissions
GroWrk MCP inherits GroWrk's existing security and permission model — authentication, role-aware access, and governance end-to-end.
› Tool call requested
list_orders(requires_customer_input: true)
Browser-based auth. No shared passwords or manual keys.
AI sees only what the authenticated user already can.
Structured tools — never raw SQL or open database access.
One workflow at a time. Validated, audit-ready.
/ FAQ
GroWrk MCP is a Model Context Protocol server that gives AI assistants governed, real-time access to your GroWrk IT lifecycle data — employees, orders, devices, retrievals, storage, SLA, and end-of-life status — from the AI tools your team already uses.
Claude, ChatGPT, Cursor, and any MCP-compatible client. You add the GroWrk MCP connector URL in your client's settings and sign in with GroWrk.
Yes. Access uses OAuth sign-in (no shared passwords or API keys), is role-aware so the AI only sees what the authenticated user can already see, exposes structured scoped tools rather than raw database access, and all writes are validated and audit-ready. It inherits GroWrk's existing security and permission model. GroWrk maintains a SOC 2 security posture.
Only the live operational data the signed-in user is already permitted to see — scoped by their role and region. The AI cannot run arbitrary queries or reach data outside the defined tools.
It can do both, but writes are deliberately constrained: one validated workflow at a time, audit-ready, never open-ended database access.
Multi-step agents (e.g. weekly end-of-life audits emailed to IT ops) and cross-system workflows that combine GroWrk data with tools like Slack, Jira, or Workday.
[ AI operating layer for IT operations ]
Governed AI access to the operational system of record for global IT lifecycle management — from visibility today to orchestration next.