Dashboard OAuth connection

Choose a test account for an OAuth-protected MCP server and understand how Manufact uses it.

When your MCP server requires OAuth, Manufact needs an upstream authorization to inspect and test the server. That authorization lives in an organization Profile. Sign in with an account at the service that hosts your MCP server and bind the profile to the server environment you are working in. Overview Connection status shows whether the selected environment is authorized and which profile is bound.

Profiles let Manufact use the protected server in Chat, the Tools, Prompts, Resources, and Skills inspector, test suites, and authenticated publish checks. The same profile binding serves interactive dashboard use and scheduled or queued runs. OAuth access and refresh tokens are encrypted at rest and refreshed in the cloud. Your Manufact login and the upstream MCP authorization are separate.

Choose a test account

We recommend a dedicated account at the upstream service for dashboard testing:

  • Give it only the permissions needed for the tools you intend to test, and review the requested OAuth scopes.
  • Give it representative sample data, without access to sensitive production data.
  • Keep it active so scheduled or later tests can still run; reconnect it when access changes or its authorization is revoked.
  • Review the upstream service's consent screen before granting access. A test connection can call tools with that account's permissions.

Avoid using an administrator or personal account just to make the dashboard show Connected. A successful connection tells you which account the dashboard can use; it does not limit what that account is allowed to do.

Connect the dashboard

  1. Open the server's Settings → Server sign-in or use Connection status on Overview.
  2. Pick an existing profile or create one, then complete OAuth with your test account. Continue only if the requested access fits your test setup.
  3. Confirm Connection status shows authorized for the environment you selected.

The displayed email comes from the upstream authorization server's UserInfo response for that profile's OAuth session. It identifies the account Manufact uses for MCP calls; it is not your Manufact login email. If the upstream service does not expose a readable email through UserInfo, the panel may show Email unavailable even when the MCP connection works. Check the upstream consent screen and run a safe test tool to confirm the account and permissions.

To change accounts, bind a different profile or reconnect the current one from Profiles or Server sign-in. Disconnecting removes the MCP grant from the profile binding for that environment; it does not delete the profile itself.

Dashboard connection versus client traffic

The bound profile is for Manufact's inspection and testing. Your users and MCP clients complete their own OAuth flows with the upstream server. Profile credentials are not used for traffic through the optional Manufact proxy. See Connecting clients for client setup.

On this page