Skip to content

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.

1

In Elaichi

Connect Ayla Networks once

  1. Open Connections, choose Add connection, and pick Ayla Networks.

  2. Optionally set Share with to give a team access, then press Connect.

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

ayla networks
Ayla Networks
BlueTally
Jamf
Iru (formerly Kandji)
ManageEngine MDM
Microsoft Intune
2

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.

Ayla Networks 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.

Ayla Networks 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 today. The plugin directory lives at chatgpt.com/plugins.

Ayla Networks 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.

Connect Ayla Networks 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.

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

See all 68 Ayla Networks tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Ayla Networks, 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 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 $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

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

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

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
ElaichiTools
Tool Action Description
Ayla Networks auth sign in Action Sign in to the Ayla IoT platform with user credentials and application details to obtain authentication tokens. Returns: user.
Ayla Networks auth SSO sign in Action Sign in to the Ayla IoT platform using a single sign-on (SSO) token from an identity provider. Returns: access_token, refresh_token. Required: token.
Ayla Networks auth validate token Validate Validate an Ayla token and return the user profile to the identity provider. Returns: response. Required: token.
Ayla Networks auth bulk update Update Update or delete an Ayla SSO user by specifying the operation and the user's unique identifier. Returns an empty 202 response on success. Required: operation, uuid.
Ayla Networks devices get registrable Get Get registrable devices in Ayla Networks available for registration via Same-LAN, Button-Push, Dsn, or Node. Returns: dsn, ip. Required: regtype. For Button-Push the button must have been pressed within the last 2 minutes; if dsn is specified other parameters are ignored.

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
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Ayla Networks · device troubleshooting and connection history

Ayla Networks starter 18 Mar 4, 2026

Engineering toolbox

Ayla Networks · device provisioning and virtual devices

— 9 Mar 2, 2026

Operations toolbox

Ayla Networks · fleet monitoring and location updates

— 24 Feb 27, 2026

Security toolbox

Ayla Networks · auth tokens and sign-in activity

Ayla Networks starter 6 Feb 19, 2026

Product toolbox

Ayla Networks · device search and lan data analysis

— 31 Jan 30, 2026

Field Services toolbox

Ayla Networks · device registration and bulk updates

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
AY

Ayla Networks (Fleet EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
AY

Ayla Networks (Fleet Americas)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
AY

Ayla Networks (Support Ops)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
AY

Ayla Networks (Engineering Prod)

Connected by Tyler Reed

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

Ayla Networks (Security Access)

Connected by Ryan Hayes

Personal • Active Not shared
AY

Ayla Networks (Field Services)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Ayla Networks Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Ayla Networks Devices Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Ayla Networks Devices List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch devices

    Ayla Networks

    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 Michael Brennan

    Approve
  6. 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

Live

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 my team share one Ayla Networks connection?

Yes. One person connects Ayla Networks with the API key and shares the connection with a team, and nobody else ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so every action against Ayla Networks is logged under the name of the person who asked for it.

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.

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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor 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.