FusionAuth (BYOK)

FusionAuth (BYOK) — connector documentation

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

What FusionAuth (BYOK) is for

FusionAuth (BYOK) lets an AI assistant read your own FusionAuth data through the FusionAuth API with a key you supply (FusionAuth API key). Read-only: 11 tools (get_system_version, list_applications, get_application, list_tenants, list_groups, list_lambdas, list_webhooks, list_themes, list_consents, list_email_templates, list_user_actions). 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 *.fusionauth.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by FusionAuth. FusionAuth 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:

• "Which FusionAuth version is our instance running?"
• "Which applications are set up in our FusionAuth instance?"
• "What roles and redirect URLs does the FusionAuth application with a given ID have?"
• "Which tenants does our FusionAuth instance have?"
• "What groups exist in FusionAuth and what roles do they carry?"
• "Which lambdas are configured in FusionAuth?"

What it does

• get_system_version: Show which FusionAuth version the instance is running.
• list_applications: List applications with name, state, tenant, OAuth client ID, enabled grants and redirect URLs. Client secrets are not returned by this tool.
• get_application: Get one application by ID: name, state, OAuth client ID, grants, redirect URLs and the roles it defines.
• list_tenants: List tenants with name, state, issuer, theme, base URL and last update. Detailed security settings are not returned by this tool.
• list_groups: List groups with name, tenant and the application roles they grant. Members are not listed.
• list_lambdas: List lambdas (custom JWT, reconcile and validation functions) with name, type, engine and debug flag. The script body is not returned by this tool.
• list_webhooks: List webhooks with description, target URL, whether they are global, and the tenants they apply to. Credentials are not returned by this tool.
• list_themes: List themes with name, type (simple or advanced) and last update. Templates and stylesheets are not returned by this tool.
• list_consents: List consent definitions with name, allowed values, self-consent age and whether several values may be granted.
• list_email_templates: List email templates with name, default subject and from address. Template bodies are not returned by this tool.
• list_user_actions: List user actions (such as warnings or timed suspensions) with name, whether they block login, and whether they are temporal.

BYOK key

You bring your own FusionAuth FusionAuth API key (https://fusionauth.io/docs/apis/authentication). 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 *.fusionauth.io 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://fusionauth.io/docs/apis/ (the API this connector calls, with a BYOK key)

Live from the FusionAuth API (*.fusionauth.io) with a BYOK key; documentation: https://fusionauth.io/docs/apis/. 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 FusionAuth. FusionAuth 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 FusionAuth account.

Built for: Worldwide. Languages: English.

FusionAuth (BYOK) — Privacy Policy

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

What FusionAuth (BYOK) is. FusionAuth (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own FusionAuth data: Read your FusionAuth Cloud applications, tenants, groups, lambdas, webhooks, themes, consents and templates with your own API key. You bring your own FusionAuth FusionAuth API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one FusionAuth 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 *.fusionauth.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If FusionAuth 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 FusionAuth receives. The request we make on your behalf, including the key and the arguments, under FusionAuth's own terms and privacy policy. FusionAuth acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer FusionAuth 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 FusionAuth 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. FusionAuth (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 FusionAuth at any time to end all access.

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

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

FusionAuth (BYOK) — Terms of Service

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

1. The Service. FusionAuth (BYOK) provides: Read your FusionAuth Cloud applications, tenants, groups, lambdas, webhooks, themes, consents and templates 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 FusionAuth credentials and only access data you are allowed to access. FusionAuth's terms apply to your use of FusionAuth; 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 FusionAuth. FusionAuth 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 FusionAuth returns, lightly trimmed; it may be incomplete, delayed or changed by FusionAuth. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your FusionAuth 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 FusionAuth'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; FusionAuth 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 FusionAuth 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 FusionAuth 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-fusionauth

FusionAuth (BYOK) support

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

• MCP endpoint: https://byok-fusionauth.connectorbay.com/mcp
• REST API: https://byok-fusionauth.connectorbay.com/openapi.json
• Live status: https://byok-fusionauth.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. FusionAuth (BYOK) never asks for them.