Okta (BYOK)

Okta (BYOK) — connector documentation

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

What Okta (BYOK) is for

Okta (BYOK) lets an AI assistant read your own Okta data through the Okta API with a key you supply (Okta API token). Read-only: 12 tools (get_org_settings, list_applications, list_groups, list_group_rules, list_authorization_servers, list_policies, list_identity_providers, list_network_zones, list_trusted_origins, list_authenticators, list_domains, list_event_hooks). 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 *.okta.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okta. Okta 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 Okta org is my token connected to?"
• "Which applications are configured in our Okta org and which are inactive?"
• "What groups exist in our Okta org?"
• "Which group assignment rules are active in Okta?"
• "Which authorization servers does our Okta org have and what are their issuers?"
• "What sign-on policies does our Okta org enforce and in which order?"

What it does

• get_org_settings: Show the Okta org the token belongs to: company name, subdomain, status, website, creation and last update dates.
• list_applications: List applications integrated with the org, with label, sign-on mode (SAML, OIDC and so on) and status. Optional search on the label and a filter expression such as status eq "ACTIVE".
• list_groups: List groups with name, description, type (OKTA_GROUP, APP_GROUP, BUILT_IN) and last membership change. Members are not listed.
• list_group_rules: List group rules that add users to groups automatically, with name, status and type.
• list_authorization_servers: List custom authorization servers with name, audiences, issuer, issuer mode and status.
• list_policies: List policies of one type (sign-on, password, access, profile enrollment, IdP discovery or OAuth authorization) with name, priority and status.
• list_identity_providers: List external identity providers (SAML, OIDC, social logins) configured for sign-in, with type, protocol and status.
• list_network_zones: List network zones used in policies and blocklists, with type, usage, status, and gateway, proxy and location counts.
• list_trusted_origins: List trusted origins allowed for CORS, redirects and iframe embedding, with origin URL, scopes and status.
• list_authenticators: List authenticators (password, phone, email, app, security key) with key, type and whether each is active.
• list_domains: List custom domains of the org with verification status and certificate source.
• list_event_hooks: List event hooks with name, status, verification status and the events they subscribe to.

BYOK key

You bring your own Okta Okta API token (https://developer.okta.com/docs/guides/create-an-api-token/main/). 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 *.okta.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://developer.okta.com/docs/api/ (the API this connector calls, with a BYOK key)

Live from the Okta API (*.okta.com) with a BYOK key; documentation: https://developer.okta.com/docs/api/. 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 Okta. Okta 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 Okta account.

Built for: Worldwide. Languages: English.

Okta (BYOK) — Privacy Policy

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

What Okta (BYOK) is. Okta (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Okta data: Read your Okta org settings, applications, groups, authorization servers, policies, identity providers, network zones and authenticators with your own API token. You bring your own Okta Okta API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Okta 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 *.okta.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 Okta 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 Okta receives. The request we make on your behalf, including the key and the arguments, under Okta's own terms and privacy policy. Okta acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Okta (BYOK) — Terms of Service

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

1. The Service. Okta (BYOK) provides: Read your Okta org settings, applications, groups, authorization servers, policies, identity providers, network zones and authenticators with your own API token. 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 Okta credentials and only access data you are allowed to access. Okta's terms apply to your use of Okta; 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 Okta. Okta 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 Okta returns, lightly trimmed; it may be incomplete, delayed or changed by Okta. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Okta 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 Okta'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; Okta 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 Okta 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 Okta 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-okta

Okta (BYOK) support

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

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