Time Tracking
Raken MCP connector
The Raken connector brings your Raken projects, time cards, work logs, materials and equipment logs to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about them and keep them current inside their own Raken access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Raken to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Raken once
-
Open Connections, choose Add connection, and pick Raken.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Raken app, then approve. Raken needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Raken MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Raken MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Raken MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Raken to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Raken through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Field operations
Catch up on yesterday's work logs
Ask what crews logged across every active Raken project yesterday and get a plain summary before the morning huddle. Follow up on any site that logged nothing.
-
Payroll
Check time cards before the pay run
Pull the week's Raken time cards by project and pay type, spot missing days or odd hours, and resolve them before payroll closes.
-
Project management
Set up a new project in minutes
Create the Raken project, confirm its child projects and budgets, and update the details as the scope changes, without clicking through every screen.
-
Procurement
See what materials sites are using
Ask which materials and units were logged on a project this month and compare them with the budget to catch overruns early.
-
Equipment
Know where equipment hours are going
Review Raken equipment logs across projects to see which machines are idle, which are overworked, and where to move them next.
-
Safety and quality
Review project notes and insights
Read the latest Raken project notes and production insights for a site and pull out the issues a superintendent needs to address today.
Try asking
- “Which Raken projects logged the most hours this week?”
- “Summarize yesterday's work logs for the Riverside project.”
- “List time cards missing a pay type for last Friday.”
Compare
Elaichi vs Zapier MCP vs Composio for Raken
All three can connect Raken to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Raken tools | Allow or restrict single Raken tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Raken call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Raken tools for your AI agents
52 tools are ready to call through Elaichi's MCP endpoint the moment you connect Raken, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Raken gets you
6 screens from the product, each doing one job for your Raken account.
The agent
Ask about Raken projects in plain language.
Get answers from live work logs, time cards and equipment logs, not yesterday's export.
- projects
- time cards
- work logs
- materials
Ask Elaichi to work across your apps.
Which Raken projects logged the most hours this week?
Summarize yesterday's work logs for the Riverside project.
List time cards missing a pay type for last Friday.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Raken in Claude, ChatGPT and Cursor.
One governed endpoint, every MCP client, no SDK and no shared API key.
Copy the endpoint
Tool catalog
52 Raken tools, ready with no code.
Projects, time cards, work logs, materials, equipment and budgets covered without writing anything.
- Create a Raken oauth revoke
- List all Raken projects
- Create a Raken project
- Get single Raken project by ID
Toolboxes
Every team gets its own Raken toolbox.
Payroll sees time cards, field ops sees work logs, each scoped to the team.
- Field operations
- Payroll
- Project management
- Procurement
Shared connections
Share Raken access, never the credential.
One person connects Raken, teams work through it without seeing a secret.
- Field Ops
- Payroll
- Project Managers
- Procurement
Audit log
Every Raken call is on the record.
Who touched which project, time card or log, and when, in one list.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Raken work logs digested before the huddle.
A schedule fetches work logs, an agent drafts the digest, a person approves it.
Raken digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Raken
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Raken
Queued
Collections and dashboards
Raken numbers refreshed without asking.
Time cards and work logs charted over 14 days, by team, with no model involved.
Raken health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Time cards
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Field Ops 34%
Payroll 27%
Project Managers 21%
Procurement 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Raken to Claude?
Connect Raken in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Raken requires an OAuth application registered inside Raken itself, so one person brings that client ID and secret once when connecting, and nobody has to handle it again. After that, each person signs in to Raken as themselves.
Does Raken work with ChatGPT and Cursor as well as Claude?
Yes. Raken is connected to Elaichi once, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. There is nothing extra to set up per client.
What can an AI agent actually do with my Raken data?
An agent can list and summarize your Raken projects, work logs, time cards, material logs, equipment logs, budgets and project notes, and it can create or update projects, materials, material units and classifications. Short concrete asks, like the hours logged on one project this week, work better than long paragraphs.
Does connecting Raken give the AI access to every project?
No. Every call runs as the person who signed in to Raken, so the agent sees the Raken projects, time cards and logs that person can already see. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Raken itself allows.
Can I stop an agent from changing things in Raken?
Yes. Restrictions in Elaichi work per action, so you can allow reading Raken work logs and time cards while blocking the creation or updating of projects and materials. A restricted action is left out of the AI client's list entirely and cannot be called, whatever the prompt says.
What happens to a Raken connection when someone leaves?
Offboarding a person in Elaichi ends their access to Raken through every AI client at once. A shared Raken connection keeps working for everyone else on the team. If you want it gone completely, disconnecting Raken once in Elaichi removes it from every client.
Does the Raken MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Raken is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Raken?
Yes. Both let Claude, ChatGPT or Cursor use Raken. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Raken call.
How is Elaichi different from Composio for Raken?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Raken: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Raken in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.