Can my team share one JobNimbus connection?

Yes. One person connects JobNimbus with their API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who sent a message or logged an activity, not the connection owner.

CRM

JobNimbus MCP connector

The JobNimbus connector brings activities, conversations, text messages and credit memos into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can log, read and update them by asking, inside each person's own JobNimbus access.

Connect on Elaichi How to connect

How it connects. Connects with an API key. 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.

30 tools

How to connect

How to connect JobNimbus to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect JobNimbus once

Open Connections, choose Add connection, and pick JobNimbus.
Optionally set Share with to give a team access, then press Connect.
Paste a JobNimbus API key. One person generates a token in JobNimbus and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

jobnimbus

All categories

JobNimbus

Affinity

Attio

Clazar

EveryAction

Follow Up Boss

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.

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 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.

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.

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.

Connect JobNimbus on Elaichi See pricing

Use cases

What teams do with JobNimbus through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

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”

See all 30 JobNimbus tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for JobNimbus, by what to check
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	$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

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.

See it in Elaichi

What connecting JobNimbus gets you

6 screens from the product, each doing one job for your JobNimbus account.

The agent

Ask about homeowner texts and get live answers.

Unread conversations, logged activities and credit memos, answered from JobNimbus in plain language.

activities
conversations
messages
credit memos

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 or Cursor

MCP clients

One endpoint brings JobNimbus to every client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

30 JobNimbus tools with no code to write.

Activities, conversations, messages and credit memos, listed, created and updated from day one.

List all JobNimbus activities
Get single JobNimbus activity by ID
Update a JobNimbus activity by ID
Delete a JobNimbus activity by ID

ElaichiTools

Tool	Action	Description
List all JobNimbus activities	List	List JobNimbus activities attached to a record or created by a user. Returns: id, content, activityTypeId, activityAction, isPrivate, primaryRecord, relatedRecords, createdAt. The API rejects requests that filter by neither primaryRecordId nor createdById. pageSize max 200, defaults to 100.
Get single JobNimbus activity by ID	Get	Get a single JobNimbus activity by id. Returns: id, content, activityTypeId, activityAction, isPrivate, primaryRecord, relatedRecords, createdAt. Required: id.
Update a JobNimbus activity by ID	Update	Update a JobNimbus activity by id with a JSON Patch document. Returns the updated activity: id, content, activityTypeId, primaryRecord, createdAt. Required: id. Activities created by a system integration or with a read-only activity type cannot be patched.
Delete a JobNimbus activity by ID	Delete	Delete a JobNimbus activity by id. Returns an empty 204 response on success. Required: id. Activities created by a system integration or with a read-only activity type cannot be deleted.
Create a JobNimbus activity	Create	Create a JobNimbus activity attached to a primary record. Returns the created activity: id, content, activityTypeId, primaryRecord, createdAt. Required: content, activityTypeId, activityAction, primaryRecord.

Toolboxes

Each team gets its own JobNimbus toolbox.

Sales logs activities, the office handles conversations, finance sees credit memos.

Sales
Office
Production
Finance

ElaichiToolboxes

Name	Source template	Tools	Created
Sales toolbox JobNimbus · estimates and follow-up activities	JobNimbus starter	18	Mar 4, 2026
Office toolbox JobNimbus · conversations and messages	—	9	Mar 2, 2026
Production toolbox JobNimbus · crew scheduling texts	—	24	Feb 27, 2026
Finance toolbox JobNimbus · credit memos	JobNimbus starter	6	Feb 19, 2026
Customer service toolbox JobNimbus · homeowner message history	—	31	Jan 30, 2026
Management toolbox JobNimbus · activity reporting across companies	—	12	Jan 22, 2026

Shared connections

Share a JobNimbus connection, never the API key.

One person connects, teams and members work through it without seeing a credential.

Sales
Office
Production
Finance

ElaichiConnections

Connection	Scope	Status	Access
JO JobNimbus (Sales) Connected by Emily Carter	Personal	• Active	1 team · 6 members
JO JobNimbus (Office) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
JO JobNimbus (Production) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
JO JobNimbus (Finance) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
JO JobNimbus (Service) Connected by Ryan Hayes	Personal	• Active	Not shared
JO JobNimbus (Canvassing) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

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.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed [email protected]	JobNimbus Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes [email protected]	JobNimbus Activities Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker [email protected]	JobNimbus Activities List	Toolbox

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

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 digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

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 Michael Brennan

Approve Deny
Post the digest

JobNimbus

Queued

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.

JobNimbus health

Refreshed 4 minutes ago · every 15 minutes · from the activities collection

Live

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%

Related connectors

More from the catalog

Browse all 500+ connectors →

FAQ

Frequently asked questions

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, 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 blocking deleting activities or messages. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.

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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Connect JobNimbus Talk to us

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.