Emerge Tools (BYOK)

Emerge Tools (BYOK) — connector documentation

• MCP endpoint: https://byok-emerge.connectorbay.com/mcp
• REST API: POST https://byok-emerge.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-emerge.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Emerge Tools Emerge Tools API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-emerge.connectorbay.com/health · Tool schemas: https://byok-emerge.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-emerge · agent@connectorbay.com

What Emerge Tools (BYOK) is for

Emerge Tools (BYOK) lets an AI assistant read your own Emerge Tools data through the Emerge Tools API with a key you supply (Emerge Tools API key). Read-only: 6 tools (list_build_history, get_build_details, get_pr_analysis, get_size_comparison_comment, get_performance_test_results, get_snapshot_comparison). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.emergetools.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Emerge Tools. Emerge Tools and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "What are the latest uploaded builds of com.example.app in Emerge?"
• "Which modules take the most space in the newest com.example.app build?"
• "How much did my pull request change the app size in Emerge?"
• "What does the Emerge size comment say for build abc123 against def456?"
• "Did the Emerge performance test t1 find a regression?"
• "Which UI snapshots changed in Emerge build abc123?"

What it does

• list_build_history: List up to 10 uploaded builds of an app with version, build number, build type, size in bytes and upload time; page with offset.
• get_build_details: Get one build's version, tag, install and download size and its size breakdown by Swift module, framework and Obj-C prefix. Without a build id the most recent upload of the app is used.
• get_pr_analysis: Get the combined result for a pull request build: app size comparison with its base, performance test results and the PR comment text. Returns not-ready until processing is done.
• get_size_comparison_comment: Get the pull request comment text and size difference between two builds, with the biggest changed files. Fails while the analysis is not ready.
• get_performance_test_results: Get performance test results for a test id: status, per-test timing, regression conclusion, percent change and device.
• get_snapshot_comparison: Get snapshot test results of a head build compared with a base build: counts and entries that were added, removed, changed or unchanged; page with page and filter by tab or name.

BYOK key

You bring your own Emerge Tools Emerge Tools API key (https://docs.emergetools.com/docs/rest-api). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.emergetools.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.emergetools.com/reference/get_apphistory-1 (the API this connector calls, with a BYOK key)

Live from the Emerge Tools API (api.emergetools.com) with a BYOK key; documentation: https://docs.emergetools.com/reference/get_apphistory-1. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Emerge Tools. Emerge Tools and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Emerge Tools account.

Built for: Worldwide. Languages: English.

Emerge Tools (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Emerge Tools (BYOK) is. Emerge Tools (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Emerge Tools data: Read your Emerge Tools mobile app size, performance test and snapshot test results with your own API key. You bring your own Emerge Tools Emerge Tools API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Emerge Tools call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.emergetools.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Emerge Tools rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Emerge Tools receives. The request we make on your behalf, including the key and the arguments, under Emerge Tools's own terms and privacy policy. Emerge Tools acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Emerge Tools gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Emerge Tools data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Emerge Tools (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Emerge Tools at any time to end all access.

Children. Emerge Tools (BYOK) is a general-audience service operated by the adult using the assistant, under Emerge Tools's own age rules.

Changes. We will post changes here with a new effective date.

Emerge Tools (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Emerge Tools (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Emerge Tools (BYOK) provides: Read your Emerge Tools mobile app size, performance test and snapshot test results with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Emerge Tools credentials and only access data you are allowed to access. Emerge Tools's terms apply to your use of Emerge Tools; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Emerge Tools. Emerge Tools and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Emerge Tools returns, lightly trimmed; it may be incomplete, delayed or changed by Emerge Tools. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Emerge Tools account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Emerge Tools's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Emerge Tools may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Emerge Tools key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Emerge Tools takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-emerge

Emerge Tools (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-emerge.connectorbay.com/mcp
• REST API: https://byok-emerge.connectorbay.com/openapi.json
• Live status: https://byok-emerge.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Emerge Tools (BYOK) never asks for them.