Aurora Solar MCP connector
The Aurora Solar connector brings your Aurora Solar users, teams, roles, partners, and single sign-on settings into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can manage the account from a chat while signed in as themselves.
-
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.
119 tools
How to connect
How to connect Aurora Solar to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Aurora Solar once
-
Open Connections, choose Add connection, and pick Aurora Solar.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Aurora Solar API key. One person generates a token in Aurora Solar 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.
Aurora Solar 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.
Aurora Solar 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.
Aurora Solar 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 Aurora Solar 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 Aurora Solar through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Bring a new designer into Aurora Solar
Invite a new hire, assign the right role, and confirm they show up on the correct team without opening the admin console.
-
IT
Deactivate a departing user the same day
Look up someone by name, deactivate their Aurora Solar user, and check that nothing was missed across teams before the offboarding ticket closes.
-
Channel
Set up a new installer partner
Create the partner record in Aurora Solar, add their first users, and update contact details as the relationship grows.
-
Sales operations
Audit who has which role
Pull the full list of Aurora Solar tenant users and roles to spot people with more access than their job needs.
-
IT
Keep single sign-on settings current
Review the SSO providers configured on your Aurora Solar tenant and update a provider when your identity setup changes.
-
Administration
Check versions before an upgrade
List the available Aurora Solar versions, schedule an upgrade, and roll back if the team runs into trouble.
Try asking
- “List Aurora Solar tenants with no active tenant users.”
- “Which tenant roles does the design team hold?”
- “Show Aurora Solar versions upgraded in the last month.”
Compare
Elaichi vs Zapier MCP vs Composio for Aurora Solar
All three can connect Aurora Solar 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 Aurora Solar tools | Allow or restrict single Aurora Solar 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 Aurora Solar 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
Aurora Solar tools for your AI agents
119 tools are ready to call through Elaichi's MCP endpoint the moment you connect Aurora Solar, 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 Aurora Solar gets you
6 screens from the product, each doing one job for your Aurora Solar account.
The agent
Ask about Aurora Solar tenants in plain language.
The agent reads live tenants, tenant users and roles, then answers in seconds.
- tenants
- tenant users
- tenant roles
- versions
Ask Elaichi to work across your apps.
List Aurora Solar tenants with no active tenant users.
Which tenant roles does the design team hold?
Show Aurora Solar versions upgraded in the last month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Reach Aurora Solar from any MCP client over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
119 Aurora Solar tools are ready to call.
Tenants, versions, tenant users and roles are covered without custom code.
- Get single Aurora Solar tenant by ID
- List all Aurora Solar tenants
- Aurora Solar tenants attach webhook
- List all Aurora Solar versions
ElaichiToolsToolboxes
Each team gets its own Aurora Solar toolbox.
Curate one toolbox per team so design sees tenants and IT sees versions.
- Design
- IT
- Operations
- Sales Engineering
ElaichiToolboxesShared connections
Teammates use Aurora Solar without a credential.
One connection, shared with named teams and members, and the login stays hidden.
- Design EMEA
- IT Platform
- Residential Sales
- Support
ElaichiConnectionsAudit log
Every Aurora Solar call is on the record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 runs the whole Aurora Solar digest.
Fetch tenants, group them, draft a digest, get approval, post back to Aurora Solar.
Aurora Solar digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tenants
Aurora Solar
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
Aurora Solar
Queued
Collections and dashboards
Aurora Solar tenant health, counted on schedule.
Four metrics, 14 days of tenants created and a per team breakdown, computed directly.
Aurora Solar health
Refreshed 4 minutes ago · every 15 minutes · from the tenants collection
Tenants
1,284 ↓ 12%
Tenant users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tenants created
Last 14 days
By team
Share of activity
Design EMEA 34%
IT Platform 27%
Residential Sales 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Aurora Solar to Claude?
First, connect Aurora Solar in Elaichi by pasting in the API key from your Aurora Solar account; there is no client ID or secret to generate and no application to register on the Aurora Solar side. Then open Claude, go to Customize, then Connectors, then Add, and paste in the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Aurora Solar is ready to use in your chats.
Does Aurora Solar work with ChatGPT and Cursor as well as Claude?
Yes. Once Aurora Solar 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 Aurora Solar once and every client picks it up.
What can an AI agent actually do with my Aurora Solar data?
With Aurora Solar connected, an agent can list your tenant users, roles, and teams, invite or create a user, update their details, and activate or deactivate them. It can also look after partner installers and their users, review and update single sign-on providers, and check available Aurora Solar versions or schedule an upgrade or rollback. Aurora Solar has a large set of actions, so short concrete asks like "deactivate Maria Lopez" work better than long paragraphs.
Does connecting Aurora Solar give the AI access to my whole tenant?
No. Every call into Aurora Solar runs under the person who signed in, so the agent can only see and change what that person's own Aurora Solar role already allows. Elaichi can narrow that access further per team or per action, and it can never widen it beyond what Aurora Solar itself grants.
Can I stop an agent from deactivating users or changing settings in Aurora Solar?
Yes. Restrictions in Elaichi apply per action, so you can allow an agent to list Aurora Solar users and roles while blocking it from deactivating anyone, changing single sign-on providers, or triggering a version upgrade. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to an Aurora Solar connection when someone leaves?
When you offboard someone in Elaichi, their access to Aurora Solar through every client ends at once. If they shared an Aurora Solar connection with a team, it keeps working for everyone else, and every past action stays in the append-only audit log under their name. If you ever want to remove Aurora Solar entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Aurora Solar MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Aurora Solar 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 Aurora Solar?
Yes. Both let Claude, ChatGPT or Cursor use Aurora Solar. 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 Aurora Solar call.
How is Elaichi different from Composio for Aurora Solar?
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 Aurora Solar: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Aurora Solar in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- 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.