External AI Clients

Staff and higher can connect supported external AI clients to Eric-backed capabilities in [REDACTED]. The client acts with your current Company permissions in the Company you authorize. These connections are separate from Company API credentials.

Who can connect a client

Staff, Admin, and Giga Admin users can create personal tokens and approve OAuth connections when MCP is enabled for their Company.
Users below Staff cannot create new connections but can still revoke their own existing ones.
Your deployment or Company may not offer MCP yet. When it is unavailable, Personal Tokens explains whether MCP is disabled for the deployment or for your Company.

Manage connections

Open Settings → Profile and scroll to Personal Tokens.

The page shows your MCP server URL, active OAuth clients and personal tokens, and actions to create, replace, or revoke access. Revoking a connection stops its credentials immediately.

Connect a client

Copy the MCP server URL from Personal Tokens into your external client’s Resplendent connection settings. Supported clients can authenticate with either:

OAuth, which sends you through Resplendent to sign in and approve access, or
A personal token you create in Personal Tokens.

OAuth approval

When a client starts OAuth, Resplendent opens a consent screen that shows the client name and return address. The client name is unverified, so approve only clients you recognize.

Choose an access level:

Read only — read accessible files and query data you can access. Saved changes, Workflow tests, and Report generation are blocked.
Read & write — read data and make changes allowed by your current Company permissions, including saved edits, Workflow tests, and Report generation where you already have authority.

OAuth authorizations expire after 90 days. Revoke them anytime from Personal Tokens.

Personal tokens

Create a token with a name and an expiry between 1 and 365 days. The secret is shown only once; store it in the client’s credential settings before closing the dialog.

Choose Read only to block saved changes, Workflow tests, and Report generation. Leave it unchecked to allow MCP actions permitted by your current Company permissions.

Replacing a personal token revokes the old token immediately and issues a new one with the access mode you select.

What the client can do

External clients use Eric-backed tools to work with data and content you can already access in Resplendent, such as:

Reading accessible Knowledge Files and Definition Files
Querying Published Data
Saving supported Knowledge and Definition File changes when write access is granted
Previewing Workflow schedules and transform samples with read access
Running No-send Workflow tests and generating Reports when write access and your role allow it

Each request uses your live Company, Source, and object permissions. Permission changes take effect on the client’s next request.

Company Knowledge proposal approval stays in the Resplendent app. Dashboard creation and Custom Integration template authoring are not available through MCP in this release.

AI credits and billing

No-send Workflow tests run through MCP can consume your AI credits and count toward your User Weekly Cap when one is set. Report generation follows the same authority and billing rules as in-app Report generation.