Device Management
Ayla Networks MCP connector
The Ayla Networks connector lets Claude, ChatGPT, Cursor 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.
-
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 Ayla Networks to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Ayla Networks once
-
Open Connections, choose Add connection, and pick Ayla Networks.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Ayla Networks API key. One person generates a token in Ayla Networks 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.
Connect Ayla Networks 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 Ayla Networks 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 Ayla Networks 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 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.
Use cases
What teams do with Ayla Networks through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Ayla Networks gets you
6 screens from the product, each doing one job for your Ayla Networks account.
The agent
Ask about your device fleet, get answers now.
Ask plain questions and get answers from live device records, no dashboard hunting required.
- devices
- tokens
- connections
- locations
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 or Cursor
MCP clients
One endpoint, every client, no shared keys.
Claude, ChatGPT and Cursor connect to Ayla Networks through one governed org endpoint.
Copy the 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.
- Ayla Networks auth sign in
- Ayla Networks auth SSO sign in
- Ayla Networks auth validate token
- Ayla Networks auth bulk update
Toolboxes
Each team gets its own device toolbox.
Ops, support and engineering each work from a toolbox scoped to their own devices.
- Support
- Engineering
- Operations
- Security
Shared connections
Shared access, credentials never change hands.
See who connected each account and how many teams and members share it.
- Fleet EMEA
- Fleet Americas
- Support Ops
- Engineering Prod
Audit log
Every device action, logged and attributable.
Every call against Ayla Networks lands in an append-only log with who and what.
- 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 triggers real work, end to end.
A trigger fetches device records, drafts a digest, and waits for a person to approve it.
Ayla Networks digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Ayla Networks
Queued
Collections and dashboards
Device health numbers, computed, not asked for.
A refreshing dashboard tracks device metrics and team breakdowns with no model involved.
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%
FAQ
Frequently asked questions
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, 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 hiding or blocking actions for a team, 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 blocking bulk updates, schedule changes or new triggers. A blocked action is never shown to the AI client at all, so no prompt, however worded, can reach it.
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 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.
Put Ayla Networks in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.