Team playbooks
Setting a single team up with governed access, in the order you would actually do it, using the systems that team already runs.
Google Analytics MCP server for marketing teams
What a Google Analytics MCP server for marketing teams actually changes: not the metrics, but which identity reads the property and where the read is recorded.
Okta MCP access for IT team: reads in Cursor, writes blocked
Okta MCP access for IT team: give IT read access to Okta users and groups from Cursor, block deactivation and app assignment, and keep connector:create tight.
Basecamp in ChatGPT for agency client status
Basecamp in ChatGPT for an agency: approvals and card tables stay readable, account staff get reads only, and the writes a client can see go to leads.
PagerDuty in Claude for on-call engineers
PagerDuty in Claude for engineers: reads and incident notes on the engineer role, while overrides, maintenance windows and every delete stay off.
Buildium in ChatGPT, read-only for accounting
Buildium in ChatGPT for a property accountant: a read-only Buildium API key, plus one Elaichi allow rule that names only the accounting reads.
Basecamp in Claude for overdue to-dos and status
Basecamp in Claude for a project team: each person on their own Basecamp sign-in, trash and project delete off the role, to-dos and comments kept.
Buildium in Claude for a property operations team
Buildium in Claude lets a property team check units, leases and work orders in chat. Scope the API key, then keep resident email and money writes off.
LeadPerfection in ChatGPT for job money
LeadPerfection in ChatGPT for a sales manager: read jobs freely, and keep the five tools that write payments, commissions and costs on one role.
LeadPerfection in Claude for reps and setters
LeadPerfection in Claude for a sales floor: one allow rule for reads and booking, the do-not-call and token tools held back, schedule boards locked.
Missive in Claude for support, minus sending
Missive in Claude for a support team: reads, posts and tasks stay open, and one block rule on the draft tool closes the send path, because it sends too.
Figma MCP access for Cursor: a governed rollout
Set up Figma MCP access for Cursor: the restrictions that stop the obvious write, and the audit query that proves they held.
Gmail and Calendar MCP access for ChatGPT
Gmail and Calendar MCP access for ChatGPT: each person signs in as themselves, and restrictions stop the AI sending or deleting mail.
Google Drive MCP access for Claude, company-wide
Google Drive MCP access for Claude, set up per person: each employee signs in as themselves, and two restrictions stop the worst failure.
Cursor access to internal tools, no shared keys
How to set up Cursor access to internal tools across an engineering team without handing anyone a provider API key.
HubSpot MCP access for sales team, per rep
HubSpot MCP access for sales team, rep by rep: each rep's own HubSpot sign-in, deal deletion and pipeline edits blocked, and an audit row that names the deal.
GitHub MCP access for Cursor: who gets which repo
GitHub MCP access for Cursor splits in two: GitHub grants the repositories, Elaichi governs which tools run and records every call.
Dynamics 365 MCP access for Claude, read-only
Dynamics 365 MCP access for Claude: the restrictions that stop a posted journal entry, and the audit row that proves nothing was written.
PagerDuty MCP server for on-call engineers
A PagerDuty MCP server for on-call engineers can run on PagerDuty's own hosted server or behind one governed endpoint, and the mechanics underneath differ.
Space permissions for Confluence in ChatGPT
ChatGPT ships no Confluence connector, so Confluence in ChatGPT runs over MCP. Here is the route that keeps each person inside their space permissions.
Google Drive in Claude for the whole company
Google Drive in Claude for a whole company: a shared connection runs as its owner, so each person connects their own Google account.
Govern SharePoint in Claude with delegated OAuth
How to keep SharePoint in Claude inside each person's own site and library permissions, using per-person OAuth and one allow rule per role.
ClickUp in ChatGPT for a customer success team
Two decisions put ClickUp in ChatGPT for a customer success team: whose account each call runs on, and which ClickUp tools are restricted.
QuickBooks read-only for a finance team in Claude
QuickBooks has no read-only OAuth scope, so QuickBooks read-only has to be enforced by whatever calls the API. Here is how to do it with one restriction.
Ramp in Claude for finance, minus admin reach
Ramp in Claude for a finance team, without giving every analyst an admin seat: one authorized connection, read-only scopes, restrictions on the finance role.
Put AI to work in your own apps
14 days of Black, no credit card. Start with one app and one team.
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