# 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. Source: https://elaichi.ai/connectors/nativebridge/ ## Facts | | | | --- | --- | | Application | NativeBridge | | Category | Application Development | | AI tools | 10 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once NativeBridge is connected - Which NativeBridge devices ran sessions this week? - List open device sessions for the Checkout application. - Show project files imported into NativeBridge yesterday. ## Connect NativeBridge in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick NativeBridge. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which NativeBridge tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect NativeBridge to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect NativeBridge to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a NativeBridge tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with NativeBridge through Elaichi ### Spin up a device to reproduce a bug QA. 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. ### Push the latest build into a project Mobile engineering. Register a new application in NativeBridge, add it to the right project, and import the fresh build without leaving the editor. ### See which apps and projects exist Product. Get a plain list of every NativeBridge project and application so a product review starts from what is actually set up, not from memory. ### Check a session while the customer waits Support. 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. ### Prepare a live demo device Sales engineering. 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. ### Tidy up finished test sessions Release management. List the project files and open sessions in NativeBridge, then delete the sessions that are no longer needed before the next release cycle begins. ## 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 my team share one NativeBridge connection? Yes. One person connects NativeBridge in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who started or ended each NativeBridge session. ### 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. ## All 10 NativeBridge tools Every tool below is callable through https://api.elaichi.ai/mcp once NativeBridge is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all NativeBridge devices** (List). List available devices in NativeBridge. Returns: id, type, osVersion, modelName, isEmulator, userPlan, magicLink, accessType, version. - **Create a NativeBridge application** (Create). Upload an Android application (APK or AAB) to NativeBridge from a file or public URL and generate a shareable magic link. Returns the uploaded app summary including id, magicLink, accessType, and version. Requires either file or apkUrl; if both are supplied, file takes precedence. - **List all NativeBridge applications** (List). List all applications uploaded by the authenticated user in NativeBridge. Returns each application with id, name, packageName, version, magicLink, access_type, and more. No parameters required. - **Create a NativeBridge device session** (Create). Create a new Android device session in NativeBridge, optionally launching a specific APK. Returns: sessionId, sessionUrl, message, id, magicLink, accessType, version. Required: deviceId. - **Get single NativeBridge session by ID** (Get). Get details of a NativeBridge session by id. Returns: id, magicLink, accessType, version. Required: id. - **Delete a NativeBridge session by ID** (Delete). Delete a NativeBridge session by id. Returns an empty 204 response on success. Required: id. - **List all NativeBridge projects** (List). List all your NativeBridge projects. Returns: id, magicLink, accessType, version. - **Create a NativeBridge project** (Create). Create a new test project in NativeBridge. Returns: id, magicLink, accessType, version. - **List all NativeBridge project files** (List). List files and folders in a NativeBridge project. Returns: id, magicLink, accessType, version. Required: project_id. - **Create a NativeBridge project import** (Create). Import an application into a nativebridge project. Returns the imported app record including id, magicLink, accessType, and version. Required: project_id.