JobTread MCP connector
The JobTread connector brings customer and vendor accounts, comments, files, budget tasks, and events into Claude, ChatGPT, Cursor, and Microsoft Copilot, where each person works inside their own JobTread access with every action logged.
- OAuth or API key
- Free 14-day trial
- No credit card
Create a vendor account for Ridgeline Plumbing with their contact details
Working in JobTread with Elaichi
-
List all JobTread account aces
-
List all JobTread account custom field values
-
List all JobTread account statement descriptors
How to connect JobTread to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
JobTread 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.
JobTread 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.
JobTread 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.
JobTread 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.
JobTread 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 JobTread 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 JobTread through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in JobTread is logged.
-
Sales
Catch the customer account up after a call
Tell the agent what changed on the call and it updates the JobTread customer account and leaves a comment so the estimator sees it before pricing starts.
-
Estimating
Add budget tasks without opening the estimate
Describe the scope line by line and the agent creates each budget task in JobTread, ready for you to price.
-
Project management
Find the comment with the change order
Ask what the client said about the kitchen tile and the agent searches JobTread comments and attached files to pull up the exact thread.
-
Office
Set up new vendors in one go
Paste a list of new subcontractors and the agent creates each vendor account in JobTread with the custom field values your office relies on.
-
Accounting
Check statement descriptors before invoices go out
Ask for every JobTread account whose statement descriptor is missing or out of date and fix them from one conversation.
-
Leadership
See who can touch which account
Ask which accounts a given person can access across JobTread, including child organizations, and tidy up access that no longer makes sense.
Try asking
- “Create a vendor account for Ridgeline Plumbing with their contact details”
- “Summarize the comments on the Harper kitchen remodel this week”
- “Add budget tasks for framing, roofing, and drywall to the Miller job”
What connecting JobTread gets you
6 screens from Elaichi, each doing one job for your JobTread account.
Ask Elaichi to work across your apps.
Create a vendor account for Ridgeline Plumbing with their contact details
Summarize the comments on the Harper kitchen remodel this week
Add budget tasks for framing, roofing, and drywall to the Miller job
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask JobTread questions in plain language.
Get answers from live accounts, comments, and budget tasks without opening JobTread.
Copy the endpoint
AI apps
One endpoint reaches JobTread from any client.
Claude, ChatGPT, and Cursor sign in over OAuth, with no SDK and no shared API key.
Tool catalog
281 JobTread tools, ready without any code.
Accounts, comments, files, budget tasks, and events, every resource and method cataloged for you.
Toolboxes
Every team gets its own JobTread toolbox.
Estimators, project managers, and the office each work from a toolbox scoped to them.
Shared connections
Share JobTread access without sharing a credential.
See who connected each account and which teams and members work through it.
Audit log
Know who changed what in JobTread.
Every call lands in an append-only log with who, what, type, and resource.
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.
JobTread digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
JobTread
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
JobTread
Queued
Workflows
A schedule starts the JobTread work itself.
New comments are fetched, grouped, drafted into a digest, approved, and posted back to JobTread.
JobTread health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Comments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Sales 34%
Estimating 27%
Project managers 21%
Office 18%
Collections and dashboards
JobTread numbers, computed with no model involved.
Four metrics, 14 days of accounts created, and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for JobTread
All three can connect JobTread 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 JobTread tools | Allow or restrict single JobTread 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 JobTread 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.
JobTread tools for your AI agents
281 tools are ready to call through Elaichi's MCP endpoint the moment you connect JobTread, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 275 of 281 JobTread tools here. Connect JobTread and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect JobTread to Claude?
Open JobTread in Elaichi and connect it with your JobTread sign-in or an API key from your JobTread settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Most people are done in a few minutes.
Does JobTread work with ChatGPT and Cursor as well as Claude?
Yes. Once JobTread 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 JobTread once and every client picks it up.
What can an AI agent actually do with my JobTread data?
It can look up customer and vendor accounts, create or update them, read and post comments, open attached files, add budget tasks, and check who has access to what in JobTread. Ask in plain words, such as the name of a customer and what changed. Short, concrete asks work better than long paragraphs.
Does connecting JobTread give the AI access to everything in my organization?
No. Every call runs as the person who signed in, so the agent sees only the JobTread accounts, comments, and child organizations that person can already open. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what JobTread grants.
Can I stop an agent from deleting or changing things in JobTread?
Yes. Restrictions in Elaichi apply per action, for example deleting a JobTread account or comment, and are set on a role or on one person. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a JobTread connection when someone leaves?
Offboarding that person in Elaichi ends their JobTread access through every client at once. A JobTread connection they shared keeps working for everyone else on the team. If you later want JobTread gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.
Does the JobTread MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. JobTread 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 JobTread?
Yes. Both let Claude, ChatGPT or Cursor use JobTread. 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 JobTread call.
How is Elaichi different from Composio for JobTread?
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 JobTread: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put JobTread 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