Fusion Auth Forms (BYOK) — connector documentation
- MCP endpoint:
https://byok-fusionauth-forms.connectorbay.com/mcp - REST API:
POST https://byok-fusionauth-forms.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-fusionauth-forms.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Fusion Auth Forms FusionAuth API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-fusionauth-forms.connectorbay.com/health· Tool schemas:https://byok-fusionauth-forms.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-fusionauth-forms · agent@connectorbay.com
What Fusion Auth Forms (BYOK) is for
Fusion Auth Forms (BYOK) lets an AI assistant read your own Fusion Auth Forms data through the Fusion Auth Forms API with a key you supply (FusionAuth API key). Read-only: 8 tools (list_forms, get_form, list_form_fields, get_form_field, list_message_templates, get_message_template, list_user_action_reasons, get_user_action_reason). 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 Fusion Auth Forms. Fusion Auth Forms 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 forms are defined in our FusionAuth instance?"
- "Which steps does FusionAuth form 5d8d4ef4-3c3e-4f7c-8f56-3d6e4b3c0a11 have?"
- "Which custom fields can be collected by FusionAuth forms?"
- "Is FusionAuth form field 6a1d4ef4-3c3e-4f7c-8f56-3d6e4b3c0a22 required?"
- "Which SMS message templates does FusionAuth have?"
- "What type is FusionAuth message template 7b2e4ef4-3c3e-4f7c-8f56-3d6e4b3c0a33?"
What it does
list_forms: List all forms (registration, admin registration, admin user and self-service user) with name, type, steps and dates.get_form: Get one form by id: name, type, steps and dates.list_form_fields: List all form fields with name, key, data type, input control, required flag and linked consent.get_form_field: Get one form field by id: name, key, data type, input control, required flag and description.list_message_templates: List SMS and voice message templates with name, type and dates. Template text is not picked.get_message_template: Get one SMS or voice message template by id: name, type and dates. Template text is not picked.list_user_action_reasons: List the reasons administrators can give when applying a user action, with code and text.get_user_action_reason: Get one user action reason by id: code, text and dates.
BYOK key
You bring your own Fusion Auth Forms 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 Fusion Auth Forms 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 Fusion Auth Forms. Fusion Auth Forms 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 Fusion Auth Forms account.
Built for: Worldwide. Languages: English.