Scheduling
Jrni MCP connector
The Jrni connector brings appointment services, bookable resources, events, locations, check-ins and client records into Claude, ChatGPT, Cursor and other AI clients, so your team can look them up and ask questions about them in plain language.
-
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.
How to connect
How to connect Jrni to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Jrni once
-
Open Connections, choose Add connection, and pick Jrni.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Jrni API key. One person generates a token in Jrni 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.
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.
Connect Jrni to 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.
Connect Jrni to 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.
Connect Jrni to 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 Jrni 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 Jrni through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Check what a location offers today
Ask which services a branch or store runs, how they are categorized, and which staff or rooms are set up to deliver them, without opening the Jrni admin.
-
Front desk
Find and update a customer's check-in
Pull up a check-in by its reference when someone arrives and update its status while the customer is still standing there.
-
Events
See what is on the events calendar
Search upcoming events, review the series they belong to, and confirm which event groups are live before promoting them.
-
Customer service
Look up a client before answering
Open a client record from Jrni during a call or chat so the answer reflects who the customer actually is.
-
Regional management
Compare services across a group of locations
List the child locations under a parent company and see how services and resources differ between them in one question.
-
Support
Trace a booking setup question quickly
When a colleague asks why a service or resource is not appearing, fetch it by reference and read its settings back in plain language.
Try asking
- “List all Jrni services with no resource assigned this week.”
- “Which Jrni resources have the most check ins today?”
- “Summarize next week's Jrni events by company.”
AI tools
Jrni tools for your AI agents
133 tools are ready to call through Elaichi's MCP endpoint the moment you connect Jrni, 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 Jrni gets you
6 screens from the product, each doing one job for your Jrni account.
The agent
Ask about bookings, get real answers.
Type a question in plain language and read it straight from live Jrni records.
- services
- resources
- check ins
- events
Ask Elaichi to work across your apps.
List all Jrni services with no resource assigned this week.
Which Jrni resources have the most check ins today?
Summarize next week's Jrni events by company.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Jrni.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
133 Jrni tools ready to call.
Services, resources, companies, events and check ins covered without custom code.
- Get single Jrni check in by ID
- Update a Jrni check in by ID
- Get single Jrni service by ID
- Jrni services get by ref
Toolboxes
Every team gets its own toolbox.
Curate Jrni toolboxes per team so each one sees only relevant tools.
- Front desk
- Operations
- Customer support
- Service design
Shared connections
Teammates book without seeing a credential.
One person connects Jrni, then shares that connection with named teams and members.
- Front desk
- Retail branches
- Operations
- Customer support
Audit log
Answer who changed which booking.
Every Jrni call lands in an append only log with actor, action and resource.
- 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
A schedule turns into a posted digest.
Jrni events are fetched, grouped, drafted by an agent, approved, then written back.
Jrni digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch services
Jrni
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
Jrni
Queued
Collections and dashboards
Jrni numbers computed, not requested.
Four metrics, 14 days of bookings created and a team breakdown, refreshed on schedule.
Jrni health
Refreshed 4 minutes ago · every 15 minutes · from the services collection
Services
1,284 ↓ 12%
Resources
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Services created
Last 14 days
By team
Share of activity
Front desk 34%
Retail branches 27%
Operations 21%
Customer support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Jrni to Claude?
First connect Jrni in Elaichi by pasting your Jrni API key, which takes a minute and needs no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Jrni services, events, locations, check-ins and clients are available in Claude.
Does Jrni work with ChatGPT and Cursor as well as Claude?
Yes. Once Jrni 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 Jrni once and every client picks it up.
What can an AI agent actually do with my Jrni data?
An agent can look up Jrni services, bookable resources, locations and their child locations, events, event groups and event series, categories, client records and check-ins, and it can update a check-in. It answers questions like which services a branch offers or what events are running this month. Short, concrete asks such as "list services at the Leeds branch" work better than long sentences.
Does connecting Jrni give the AI access to every location and company?
No. Every call to Jrni runs inside the access of the person who signed in, so an agent sees the companies, locations and records that person can already see. Elaichi can narrow that further per person or team, and it can never widen it beyond what Jrni itself allows.
Can I stop an agent from changing check-ins or other records in Jrni?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Jrni services, events and clients while blocking the ability to update a check-in. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Jrni connection when someone leaves?
Offboarding that person in Elaichi ends their access to Jrni through every AI client at once. A shared Jrni connection keeps working for everyone else on the team. If you ever want to remove Jrni entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Put Jrni in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.