Application Development · Beta

NativeBridge
API integration

Ship Application Development features without building the integration. Full NativeBridge API access via Proxy and 10+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us

Use Cases

Why integrate with NativeBridge

Common scenarios for SaaS companies building NativeBridge integrations for their customers.

01

Embed live mobile app previews in no-code builders

No-code and low-code mobile builders can let users preview their compiled iOS/Android apps directly in the browser without leaving the dashboard. Truto handles the NativeBridge auth and session lifecycle so your platform can focus on the build-to-preview flow.

02

Attach reproducible mobile bug sessions to tickets

Issue trackers and QA platforms can generate a live device session for the exact APK/AAB tied to a bug report and attach the Magic Link to the ticket. Developers reproduce mobile bugs in one click instead of provisioning devices locally.

03

Broadcast build previews to reviewers in CI/CD tools

DevOps and collaboration platforms can automatically ingest new mobile builds into a NativeBridge project and push the shareable session link to reviewers. Product managers and clients approve mobile iterations without installing anything.

04

Orchestrate cloud device sessions for automated test runs

Test automation and QA orchestration platforms can programmatically provision devices matching specific OS versions or models, run tests against the session, and tear down sessions to control concurrency and cost.

05

Maintain multi-version app history for client QA portals

Agencies and client-facing QA platforms can organize their customers' app builds under NativeBridge projects and import new versions on each release. End users get a browsable history of testable app versions per client.

What You Can Build

Ship these features with Truto + NativeBridge

Concrete product features your team can ship faster by leveraging Truto’s NativeBridge integration instead of building from scratch.

01

One-click mobile app preview links

Upload an APK or AAB via the NativeBridge application endpoint and surface the returned Magic Link inside your product's UI.

02

In-app embedded device emulator

Create a device session and embed the returned session URL in an iframe so users interact with their native mobile app inside your web dashboard.

03

Device targeting selector

List available NativeBridge devices and let users pick target OS version, model, or emulator vs. real hardware before launching a session.

04

Session lifecycle controls

Poll session status by ID and expose a delete action so users can monitor active sessions and free up concurrency limits from within your product.

05

Project-based build history

Create NativeBridge projects per customer or app, import new builds on each release, and list project files to render a version timeline.

06

Automated build-to-review workflows

Trigger an application upload and device session creation as part of your CI/CD flow, then post the resulting Magic Link into review channels.

SuperAI

NativeBridge AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_native_bridge_devices

List available devices in NativeBridge. Returns: id, type, osVersion, modelName, isEmulator, userPlan, magicLink, accessType, version.

create_a_native_bridge_application

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_native_bridge_applications

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_native_bridge_device_session

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_native_bridge_session_by_id

Get details of a NativeBridge session by id. Returns: id, magicLink, accessType, version. Required: id.

delete_a_native_bridge_session_by_id

Delete a NativeBridge session by id. Returns an empty 204 response on success. Required: id.

list_all_native_bridge_projects

List all your NativeBridge projects. Returns: id, magicLink, accessType, version.

create_a_native_bridge_project

Create a new test project in NativeBridge. Returns: id, magicLink, accessType, version.

list_all_native_bridge_project_files

List files and folders in a NativeBridge project. Returns: id, magicLink, accessType, version. Required: project_id.

create_a_native_bridge_project_import

Import an application into a nativebridge project. Returns the imported app record including id, magicLink, accessType, and version. Required: project_id.

Why Truto

Why use Truto’s MCP server for NativeBridge

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 600+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with NativeBridge in under an hour. No boilerplate, no maintenance burden.

01

Link your customer’s NativeBridge account

Use Truto’s frontend SDK to connect your customer’s NativeBridge account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call NativeBridge

Truto’s Proxy API is a 1-to-1 mapping of the NativeBridge API. You call us, we call NativeBridge, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate NativeBridge’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about NativeBridge on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does Truto handle authentication with NativeBridge?

Truto manages the NativeBridge credentials your end users provide and injects them into every API call. Your product never has to store or rotate NativeBridge API keys directly.

What NativeBridge operations are supported today?

The current toolkit covers applications (create and list), device sessions (create, get by ID, delete), device discovery (list), and projects (create, list, list files, create import). Additional endpoints can be added on request.

Can I upload an APK or AAB through the integration?

Yes. The create application tool ingests an APK or AAB (typically via a public URL or file reference) and returns the NativeBridge application ID plus the shareable Magic Link.

Can end users choose which device their app runs on?

Yes. Use the list devices tool to fetch available environments, then pass the selected device into the create device session tool to launch the app on that specific OS version, model, or emulator/real-device target.

How do we manage concurrency and clean up idle sessions?

You can poll session state using the get session by ID tool and programmatically remove sessions with the delete session tool. This lets you enforce your own concurrency and cost limits per customer.

Is there a unified API for this integration?

NativeBridge is exposed today through direct tool calls rather than a unified API, since it's a specialized mobile app hosting category. You interact with it through Truto's Passthrough and tool-call interfaces using a consistent auth and request model.

NativeBridgeAPI integration