SSO
Torii MCP connector
Connect Torii to Elaichi and your app inventory, users, contracts, and audit logs become available to Claude, ChatGPT, Cursor, and the Elaichi Agent, with each person working inside their own Torii access and every call logged.
-
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 Torii to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Torii once
-
Open Connections, choose Add connection, and pick Torii.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Torii API key. One person generates a token in Torii 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.
Google Workspace
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 Torii 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 Torii 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 Torii 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 Torii 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 Torii through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Check who still uses an app before renewal
Ask which people are assigned to a given application in Torii and how many of them are still active, so the renewal conversation starts with real numbers instead of a guess.
-
Finance
Pull every contract renewing this quarter
List the Torii contracts coming up for renewal, compare their values, and update a contract's terms or owner once the vendor confirms the new pricing.
-
Procurement
Log a new contract the day it is signed
Create the contract record in Torii, attach the signed PDF, and link it to the right application so nobody has to hunt for the paperwork later.
-
Security
Review what changed in Torii and who did it
Read the Torii audit log to see which users, applications, and contracts were edited, and check role assignments when an access review comes around.
-
People operations
Confirm a leaver's app list during offboarding
Look up every application a departing employee holds in Torii, mark them as offboarded, and update their user record so the license count is right by the end of the day.
-
IT
Add a newly discovered app to the inventory
Search Torii to see whether a tool someone expensed is already tracked, and if not, create the app record and assign an owner so it stops being shadow IT.
Try asking
- “List Torii applications with no active users this quarter.”
- “Which Torii contracts renew in the next 60 days?”
- “Show users in Torii holding more than ten applications.”
AI tools
Torii tools for your AI agents
26 tools are ready to call through Elaichi's MCP endpoint the moment you connect Torii, 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 Torii gets you
6 screens from the product, each doing one job for your Torii account.
The agent
Ask about Torii licenses, read live answers.
Type a question in plain language and get answers from live Torii records.
- users
- applications
- contracts
- roles
Ask Elaichi to work across your apps.
List Torii applications with no active users this quarter.
Which Torii contracts renew in the next 60 days?
Show users in Torii holding more than ten applications.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Torii here.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
26 Torii tools arrive ready to call.
Users, applications, contracts and roles are covered with no custom code to write.
- List all Torii me
- List all Torii users
- Get single Torii user by ID
- Update a Torii user by ID
Toolboxes
Every team gets its own Torii toolbox.
Curate one toolbox per team so each group sees only the Torii tools it needs.
- IT Operations
- Finance
- Security
- Procurement
Shared connections
Teammates use Torii without holding the credential.
Each connection shows who connected the account and which teams and members share it.
- IT Operations
- Finance
- Security
- Procurement
Audit log
Every Torii call is written down.
When, who, what happened, type and resource, appended for each Torii request.
- 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 fires, a Torii digest ships.
Six steps fetch and group Torii records, draft a digest, then post after approval.
Torii digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
Torii
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
Torii
Queued
Collections and dashboards
Torii license numbers land before anyone asks.
Four metrics, 14 days of records created and a team breakdown, computed on a schedule.
Torii health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Applications
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT Operations 34%
Finance 27%
Security 21%
Procurement 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Torii to Claude?
Two steps. First, connect Torii in Elaichi by pasting a Torii API key, which you can generate from your Torii admin settings; there is no OAuth application to register and no client ID or secret to create. Second, open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude then asks you to sign in to Elaichi, and from that point Torii is available inside your conversations.
Does Torii work with ChatGPT and Cursor as well as Claude?
Yes. Once Torii 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 Torii once and use it from whichever client you happen to be working in.
What can an AI agent actually do with my Torii data?
With Torii connected, an agent can look up the applications in your inventory, see which people are assigned to each one, and read or update user records. It can list, create, update, and delete contracts, attach files such as signed agreements, search for an app by name, and read the Torii audit log and workflow history. In practice that means asking questions like which contracts renew next month, or which apps a leaving employee still holds, and getting an answer from live Torii records.
Does connecting Torii give the AI access to my whole Torii workspace?
No. Every call to Torii runs with the access of the person who signed in to Elaichi, so an agent sees only the applications, users, and contracts that person could already see in Torii. Elaichi can narrow that access further, for example by blocking contract deletion for a whole team, but it can never grant more than the person's own Torii permissions allow.
Can I stop an agent from deleting or changing things in Torii?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Torii contracts and applications while blocking deletion, or allow user lookups while blocking updates. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so there is no prompt, accidental or otherwise, that can reach it.
What happens to a Torii connection when someone leaves?
When you offboard a person in Elaichi, their access to Torii through every connected client ends immediately, and a shared Torii connection keeps working for everyone else on the team. If you want to remove Torii entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Torii in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.