NativeBridge MCP connector
The NativeBridge connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent list your cloud devices, projects, apps, and files, start and end device sessions, and import builds, with every action tied to the person who asked.
- Connects with an API key
- Free 14-day trial
- No credit card
Which NativeBridge devices ran sessions this week?
Working in NativeBridge with Elaichi
-
List all NativeBridge devices
-
List all NativeBridge applications
-
Get single NativeBridge session by ID
How to connect NativeBridge to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
NativeBridge 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.
NativeBridge 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.
NativeBridge 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.
NativeBridge 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.
NativeBridge 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 NativeBridge 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 NativeBridge through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in NativeBridge is logged.
-
QA
Spin up a device to reproduce a bug
Ask for the list of available NativeBridge devices, start a session on the model a customer reported, and close it when the check is done.
-
Mobile engineering
Push the latest build into a project
Register a new application in NativeBridge, add it to the right project, and import the fresh build without leaving the editor.
-
Product
See which apps and projects exist
Get a plain list of every NativeBridge project and application so a product review starts from what is actually set up, not from memory.
-
Support
Check a session while the customer waits
Look up a NativeBridge session by its ID to confirm the device, the app under test, and whether it is still running before replying to a ticket.
-
Sales engineering
Prepare a live demo device
Start a NativeBridge device session on the handset a prospect uses, then end it as soon as the call wraps so nothing is left running.
-
Release management
Tidy up finished test sessions
List the project files and open sessions in NativeBridge, then delete the sessions that are no longer needed before the next release cycle begins.
Try asking
- “Which NativeBridge devices ran sessions this week?”
- “List open device sessions for the Checkout application.”
- “Show project files imported into NativeBridge yesterday.”
What connecting NativeBridge gets you
6 screens from Elaichi, each doing one job for your NativeBridge account.
Ask Elaichi to work across your apps.
Which NativeBridge devices ran sessions this week?
List open device sessions for the Checkout application.
Show project files imported into NativeBridge yesterday.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about devices and sessions in plain language.
Answers come from live NativeBridge projects, applications, devices and sessions.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach NativeBridge here.
One governed org endpoint over OAuth, no SDK and no shared API key.
Tool catalog
10 NativeBridge tools ready without custom code.
Applications, devices, sessions, projects and project files, each with its methods listed.
Toolboxes
Every team gets its own NativeBridge toolbox.
Mobile QA, platform and release each see a toolbox scoped to their work.
Shared connections
Teammates run device sessions without seeing credentials.
Each NativeBridge connection shows who connected it and which teams and members share it.
Audit log
Answer who deleted that NativeBridge session.
Append-only rows record when, who, what happened, the type and the resource.
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.
NativeBridge digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch devices
NativeBridge
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
NativeBridge
Queued
Automations
A schedule drives a NativeBridge digest end to end.
Six steps fetch sessions, group them, draft a digest, take approval, then post back.
NativeBridge health
Refreshed 4 minutes ago · every 15 minutes · from the devices collection
Devices
1,284 ↓ 12%
Applications
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Devices created
Last 14 days
By team
Share of activity
Mobile QA 34%
Platform 27%
Release Engineering 21%
Developer Experience 18%
Collections and dashboards
NativeBridge project health, computed not requested.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for NativeBridge
All three can connect NativeBridge 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 NativeBridge tools | Allow or restrict single NativeBridge 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 NativeBridge 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.
NativeBridge tools for your AI agents
10 tools are ready to call through Elaichi's MCP endpoint the moment you connect NativeBridge, 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 NativeBridge to Claude?
Connect NativeBridge in Elaichi first, then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. NativeBridge connects with an API key, so the sign-in step is pasting the key from your NativeBridge account into Elaichi. There is no OAuth application to register and no client ID or secret to generate.
Does NativeBridge work with ChatGPT and Cursor as well as Claude?
Yes. Once NativeBridge 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 NativeBridge once and every client picks it up.
What can an AI agent actually do with my NativeBridge account?
An agent can list the devices, applications, projects, and project files in your NativeBridge account, and register a new application or project. It can start a device session, look one up by its ID, end it, and import a build into a project. It cannot do anything in NativeBridge beyond those actions.
Does connecting NativeBridge give the AI access to every device and project?
No. Every request to NativeBridge runs inside the access of the person who signed in, so the agent only sees the devices, projects, and sessions that person's NativeBridge key can reach. Elaichi can narrow that further with restrictions, and it never widens what NativeBridge itself allows.
Can I stop an agent from deleting or changing things in NativeBridge?
Yes. Restrictions in Elaichi apply per action, so you can allow listing NativeBridge devices and projects while restricting session deletion, application creation, or build imports. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a NativeBridge connection when someone leaves?
Offboarding a person in Elaichi ends their access to NativeBridge at once, across every client they used. A shared NativeBridge connection keeps working for everyone else on the team. If you want to remove NativeBridge entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent together.
Does the NativeBridge MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. NativeBridge 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 NativeBridge?
Yes. Both let Claude, ChatGPT or Cursor use NativeBridge. 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 NativeBridge call.
How is Elaichi different from Composio for NativeBridge?
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 NativeBridge: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put NativeBridge 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