Application Development
NativeBridge MCP connector
The NativeBridge connector lets Claude, ChatGPT, Cursor, 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.
-
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.
10 tools
How to connect
How to connect NativeBridge to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect NativeBridge once
-
Open Connections, choose Add connection, and pick NativeBridge.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a NativeBridge API key. One person generates a token in NativeBridge 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 NativeBridge 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 NativeBridge 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 NativeBridge 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 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.
Use cases
What teams do with NativeBridge through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting NativeBridge gets you
6 screens from the product, each doing one job for your NativeBridge account.
The agent
Ask about devices and sessions in plain language.
Answers come from live NativeBridge projects, applications, devices and sessions.
- devices
- applications
- sessions
- projects
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach NativeBridge here.
One governed org endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
10 NativeBridge tools ready without custom code.
Applications, devices, sessions, projects and project files, each with its methods listed.
- List all NativeBridge devices
- Create a NativeBridge application
- List all NativeBridge applications
- Create a NativeBridge device session
ElaichiToolsToolboxes
Every team gets its own NativeBridge toolbox.
Mobile QA, platform and release each see a toolbox scoped to their work.
- Mobile QA
- Platform
- Release Engineering
- Developer Experience
ElaichiToolboxesShared connections
Teammates run device sessions without seeing credentials.
Each NativeBridge connection shows who connected it and which teams and members share it.
- Mobile QA
- Platform
- Release Engineering
- Developer Experience
ElaichiConnectionsAudit log
Answer who deleted that NativeBridge session.
Append-only rows record when, who, what happened, the type and the resource.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 drives a NativeBridge digest end to end.
Six steps fetch sessions, group them, draft a digest, take approval, then post back.
NativeBridge digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
NativeBridge
Queued
Collections and dashboards
NativeBridge project health, computed not requested.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
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%
FAQ
Frequently asked questions
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, 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 blocking session deletion, application creation, or build imports. A blocked action is never advertised to Claude, ChatGPT, or Cursor, so no prompt can reach it.
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, and the Elaichi Agent together.
Put NativeBridge in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.