JobNimbus MCP connector
The JobNimbus connector brings activities, conversations, text messages and credit memos into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can log, read and update them by asking, inside each person's own JobNimbus access.
- Connects with an API key
- Free 14-day trial
- No credit card
Log a call with the Henderson roof estimate as a JobNimbus activity
Working in JobNimbus with Elaichi
-
List all JobNimbus activities
-
Get single JobNimbus activity by ID
-
List all JobNimbus activity types
How to connect JobNimbus to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
JobNimbus 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.
JobNimbus MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
JobNimbus 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. The plugin directory lives at chatgpt.com/plugins.
JobNimbus 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.
JobNimbus MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect JobNimbus 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.
What teams do with JobNimbus through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in JobNimbus is logged.
-
Sales
Log the call before leaving the driveway
After an estimate visit, tell the agent what happened and it creates the activity in JobNimbus with the right activity type, so the follow-up is on the record before you reach the next stop.
-
Office
Clear the morning's unread text conversations
Ask which JobNimbus conversations are still unread, get a summary of what each homeowner wrote, and mark the ones you have handled as read in one pass.
-
Production
Text the crew schedule to the homeowner
Draft and send the message in the existing JobNimbus conversation, then log an activity noting the confirmed install date.
-
Finance
Review credit memos before month end
Pull the list of JobNimbus credit memos issued this month and ask for the ones over a set amount or tied to a particular company.
-
Customer service
Catch up on a homeowner's full message history
Before returning a call, ask for every message in that JobNimbus conversation and get a short summary of what was promised and when.
-
Management
Bulk-load activities from a canvassing day
Hand the agent the list of doors knocked and it creates the activities in JobNimbus in one batch, each with the right type, instead of someone typing them in one by one.
Try asking
- “Log a call with the Henderson roof estimate as a JobNimbus activity”
- “Which conversations are still unread from this morning?”
- “List credit memos issued this month over 500 dollars”
What connecting JobNimbus gets you
6 screens from Elaichi, each doing one job for your JobNimbus account.
Ask Elaichi to work across your apps.
Log a call with the Henderson roof estimate as a JobNimbus activity
Which conversations are still unread from this morning?
List credit memos issued this month over 500 dollars
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about homeowner texts and get live answers.
Unread conversations, logged activities and credit memos, answered from JobNimbus in plain language.
Copy the endpoint
AI apps
One endpoint brings JobNimbus to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared API key.
Tool catalog
30 JobNimbus tools with no code to write.
Activities, conversations, messages and credit memos, listed, created and updated from day one.
Toolboxes
Each team gets its own JobNimbus toolbox.
Sales logs activities, the office handles conversations, finance sees credit memos.
Shared connections
Share a JobNimbus connection, never the API key.
One person connects, teams and members work through it without seeing a credential.
Audit log
Every JobNimbus call is recorded with a name.
When, who, what happened, type and resource, in an append-only log you can search.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
JobNimbus digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch activities
JobNimbus
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 Jake Morgan
Approve Deny -
Post the digest
JobNimbus
Queued
Workflows
A schedule turns unread texts into a digest.
Conversations are fetched, grouped and drafted, a person approves, and the summary posts back to JobNimbus.
JobNimbus health
Refreshed 4 minutes ago · every 15 minutes · from the activities collection
Activities
1,284 ↓ 12%
Conversations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Activities created
Last 14 days
By team
Share of activity
Sales 34%
Office 27%
Production 21%
Finance 18%
Collections and dashboards
JobNimbus activity counts, computed with no model involved.
Four metrics, 14 days of activities created, and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for JobNimbus
All three can connect JobNimbus 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 JobNimbus tools | Allow or restrict single JobNimbus 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 JobNimbus 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 | Free for one person; $15 per user per month on Gold. | 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.
JobNimbus tools for your AI agents
30 tools are ready to call through Elaichi's MCP endpoint the moment you connect JobNimbus, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect JobNimbus to Claude?
Connect JobNimbus in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. JobNimbus connects with an API key, so the sign-in step is pasting the key from your JobNimbus account settings into Elaichi. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes.
Does JobNimbus work with ChatGPT and Cursor as well as Claude?
Yes. Once JobNimbus is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect JobNimbus once and every client you use picks it up.
What can an AI agent actually do with my JobNimbus data?
It can read and create JobNimbus activities, open text conversations and the messages in them, send a reply, mark conversations read or unread, and list credit memos and the companies in your account. In practice that means logging a call after a visit, summarizing what a homeowner texted, or pulling this month's credit memos by asking. Short concrete asks, like "log a call on the Henderson job", work better than long sentences.
Does connecting JobNimbus give the AI everything in my account?
No. Every call runs inside the access of the person who signed in, so the AI sees the JobNimbus activities, conversations and credit memos that person can already see, and nothing more. Elaichi can narrow that further with restrictions, and it can never widen it beyond what JobNimbus already allows.
Can I stop an agent from deleting or changing things in JobNimbus?
Yes. Restrictions in Elaichi work per action, so you can allow reading and creating JobNimbus activities while restricting deleting activities or messages. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a JobNimbus connection when someone leaves?
Offboarding someone in Elaichi ends their access to JobNimbus through every AI client at once. If they had shared a JobNimbus connection, it keeps working for everyone else on the team. Disconnecting JobNimbus once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the JobNimbus MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. JobNimbus 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, Microsoft Copilot, 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 JobNimbus?
Yes. Both let Claude, ChatGPT or Cursor use JobNimbus. 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 JobNimbus call.
How is Elaichi different from Composio for JobNimbus?
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 JobNimbus: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put JobNimbus in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot