Ayla Networks MCP connector
The Ayla Networks connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and other AI clients look up connected devices, check connection history, set schedules and triggers, and update device records in Ayla Networks, with each person signed in as themselves and every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Show devices offline for more than 24 hours.
Working in Ayla Networks with Elaichi
-
Ayla Networks devices get registrable
-
List all Ayla Networks devices
-
Ayla Networks devices get connection history
How to connect Ayla Networks to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Ayla Networks 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.
Ayla Networks MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
Ayla Networks 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. The plugin directory lives at chatgpt.com/plugins.
Ayla Networks 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.
Ayla Networks MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 Ayla Networks 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.
What teams do with Ayla Networks through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Ayla Networks is logged.
-
Support
Find a customer's device and check its status
Search Ayla Networks for the device a caller is describing, pull up its details and connection history, and see whether it has dropped offline before the customer finishes explaining the problem.
-
Field service
Update device locations after an install
When a technician finishes an installation, catch the device record up with its new location in Ayla Networks and confirm it has registered correctly.
-
Operations
Set schedules across a fleet at once
Update schedules and schedule actions for many devices in one pass in Ayla Networks, rather than opening each device and editing it by hand.
-
Product
Define a new device template
Create a template and its properties in Ayla Networks when a new product model is ready, so devices coming off the line register against the right definition.
-
Engineering
Spin up virtual devices for testing
Create virtual devices in Ayla Networks to test firmware behavior, triggers and notifications before real hardware ships.
-
Operations
Set up alerts for device events
Create notification apps and triggers in Ayla Networks so the right people hear about a device going offline or a reading crossing a threshold.
Try asking
- “Show devices offline for more than 24 hours.”
- “List all devices registered to the EMEA team.”
- “Summarize connection history for device DVC-4821.”
What connecting Ayla Networks gets you
6 screens from Elaichi, each doing one job for your Ayla Networks account.
Ask Elaichi to work across your apps.
Show devices offline for more than 24 hours.
List all devices registered to the EMEA team.
Summarize connection history for device DVC-4821.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your device fleet, get answers now.
Ask plain questions and get answers from live device records, no dashboard hunting required.
Copy the endpoint
AI apps
One endpoint, every client, no shared keys.
Claude, ChatGPT, Cursor and Microsoft Copilot connect to Ayla Networks through one governed org endpoint.
Tool catalog
68 Ayla Networks tools, zero custom code.
Every device, auth and lan tool cataloged and ready, with no custom code to write.
Toolboxes
Each team gets its own device toolbox.
Ops, support and engineering each work from a toolbox scoped to their own devices.
Shared connections
Shared access, credentials never change hands.
See who connected each account and how many teams and members share it.
Audit log
Every device action, logged and attributable.
Every call against Ayla Networks lands in an append-only log with who and what.
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.
Ayla Networks digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch devices
Ayla Networks
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 Jake Morgan
Approve Deny -
Post the digest
Ayla Networks
Queued
Automations
A schedule triggers real work, end to end.
A trigger fetches device records, drafts a digest, and waits for a person to approve it.
Ayla Networks health
Refreshed 4 minutes ago · every 15 minutes · from the devices collection
Devices
1,284 ↓ 12%
Tokens
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Devices created
Last 14 days
By team
Share of activity
Fleet EMEA 34%
Fleet Americas 27%
Support Ops 21%
Engineering Prod 18%
Collections and dashboards
Device health numbers, computed, not asked for.
A refreshing dashboard tracks device metrics and team breakdowns with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Ayla Networks
All three can connect Ayla Networks 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 Ayla Networks tools | Allow or restrict single Ayla Networks 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 Ayla Networks 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.
Ayla Networks tools for your AI agents
68 tools are ready to call through Elaichi's MCP endpoint the moment you connect Ayla Networks, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Ayla Networks to Claude?
Connect Ayla Networks in Elaichi first, which means pasting in your Ayla Networks API key. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and Ayla Networks is ready to use.
Does Ayla Networks work with ChatGPT and Cursor as well as Claude?
Yes. Once Ayla Networks 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 Ayla Networks once and every client picks it up.
What can an AI agent actually do with my Ayla Networks data?
With Ayla Networks connected, an agent can find a device, pull its details and connection history, list devices that are ready to register, update locations, set schedules and triggers, create templates and notification apps, and record datapoints. Because Ayla Networks has many possible actions, short concrete asks like "show connection history for device 4821" work better than long sentences.
Does connecting Ayla Networks give the AI access to every device in my account?
No. Every action runs as the person who signed in, so an agent only sees the Ayla Networks devices, templates and schedules that person can already see. Elaichi can narrow that further by restricting actions for a role, but it can never grant more access to Ayla Networks than the person already has.
Can I stop an agent from changing or updating devices in Ayla Networks?
Yes. Restrictions in Elaichi apply action by action, so you can allow looking up Ayla Networks devices and connection history while restricting bulk updates, schedule changes or new triggers. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Ayla Networks connection when someone leaves?
Offboarding a person in Elaichi ends their access to Ayla Networks immediately, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Ayla Networks connection keeps working for everyone else on the team. If you ever want to remove Ayla Networks entirely, disconnecting it once in Elaichi removes it from every client at the same time.
Does the Ayla Networks MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Ayla Networks 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 Ayla Networks?
Yes. Both let Claude, ChatGPT or Cursor use Ayla Networks. 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 Ayla Networks call.
How is Elaichi different from Composio for Ayla Networks?
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 Ayla Networks: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Ayla Networks 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