Skip to content

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, Microsoft Copilot, and the Elaichi Agent, so each person can manage the account from a chat while signed in as themselves.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List Aurora Solar tenants with no active tenant users.

Working in Aurora Solar with Elaichi

  • Get single Aurora Solar tenant by ID
  • List all Aurora Solar tenants
  • List all Aurora Solar versions
Ask anything…
Governance / Audit log Last 24 hours
Aurora Solar List all Aurora Solar versions Emily Carter · Claude · 9:41 AM Done
Aurora Solar List all Aurora Solar tenants Emily Carter · Claude · 9:41 AM Done
Aurora Solar Get single Aurora Solar tenant by ID Emily Carter · Claude · 9:41 AM Done
Aurora Solar Aurora Solar tenants attach webhook Megan Brooks · ChatGPT · 9:38 AM Done
Aurora Solar Create a Aurora Solar versions upgrade Ryan Hayes · Cursor · 9:35 AM Done

How to connect Aurora Solar to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Aurora Solar MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 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.

Aurora Solar MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Aurora Solar MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Aurora Solar MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Aurora Solar to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Aurora Solar through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Aurora Solar is logged.

  • 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.”

See all 119 Aurora Solar tools →

What connecting Aurora Solar gets you

6 screens from Elaichi, each doing one job for your Aurora Solar account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about Aurora Solar tenants in plain language.

The agent reads live tenants, tenant users and roles, then answers in seconds.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.

Reach Aurora Solar from any MCP client over OAuth, no SDK, no shared key.

ElaichiTools
Tool Action Description
Get single Aurora Solar tenant by ID Get Retrieve metadata about an Aurora Solar tenant by id. Returns: tenant, id, address, latitude, longitude, description. Required: id.
List all Aurora Solar tenants List List webhooks for an Aurora Solar tenant, sorted in descending creation-date order. Returns each webhook's id, description, event, url_template, and enabled status. Required: tenant_id.
Aurora Solar tenants attach webhook Action Create a new webhook for an Aurora Solar tenant. Returns: webhook, id, description, created_at, updated_at. Required: id, event, url_template.
List all Aurora Solar versions List Retrieve the current, latest, and rollback API versions associated with the authenticated bearer token in Aurora Solar. Returns: current, latest, rollback, rollback_expire_at. No required parameters.
Create a Aurora Solar versions upgrade Create Upgrade your Aurora Solar API version to the latest available version. Returns: current, latest, rollback, rollback_expire_at. The rollback window is 5 days (120 hours) after upgrade. No request body is required.

Tool catalog

119 Aurora Solar tools are ready to call.

Tenants, versions, tenant users and roles are covered without custom code.

ElaichiToolboxes
Name Source template Tools Created

Design toolbox

Aurora Solar · tenants and projects

Aurora Solar starter 18 Mar 4, 2026

IT toolbox

Aurora Solar · versions and upgrades

— 9 Mar 2, 2026

Operations toolbox

Aurora Solar · tenant users and activation

— 24 Feb 27, 2026

Sales Engineering toolbox

Aurora Solar · tenants and roles

Aurora Solar starter 6 Feb 19, 2026

Support toolbox

Aurora Solar · tenant users and invites

— 31 Jan 30, 2026

Security toolbox

Aurora Solar · tenant roles and webhooks

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Aurora Solar toolbox.

Curate one toolbox per team so design sees tenants and IT sees versions.

ElaichiConnections
Connection Scope Status Access
AU

Aurora Solar (Design EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
AU

Aurora Solar (IT Platform)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
AU

Aurora Solar (Residential Sales)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
AU

Aurora Solar (Support)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
AU

Aurora Solar (Operations)

Connected by Ryan Hayes

Personal • Active Not shared
AU

Aurora Solar (Commercial Projects)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Aurora Solar without a credential.

One connection, shared with named teams and members, and the login stays hidden.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Aurora Solar Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Aurora Solar Tenants Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Aurora Solar Tenants List Toolbox

Audit log

Every Aurora Solar call is on the record.

When, who, what happened, type and resource, appended and never edited.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Aurora Solar digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch tenants

    Aurora Solar

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Aurora Solar

    Queued

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 health

Refreshed 4 minutes ago · every 15 minutes · from the tenants collection

Live

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%

Collections and dashboards

Aurora Solar tenant health, counted on schedule.

Four metrics, 14 days of tenants created and a per team breakdown, computed directly.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Aurora Solar, by what to check
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 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.

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.

Questions, answered

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, Microsoft Copilot, 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 my team share one Aurora Solar connection?

Yes. One administrator connects Aurora Solar in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who invited a user or deactivated one in Aurora Solar, not just that the shared connection was used.

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 restricting it from deactivating anyone, changing single sign-on providers, or triggering a version upgrade. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot, 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, 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 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 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