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, the Manufact dashboard needs its own connection to inspect and test the server. Sign in with an account at the service that hosts your MCP server. This is the authenticated test account shown below Connection Status on the server's Overview page.
This connection lets Manufact use the protected server in Chat, the Tools, Prompts, and Resources inspector, test suites, and authenticated publish checks. Manufact saves the dashboard credentials on the server so background tests can use them. OAuth access and refresh tokens are encrypted at rest. Your Manufact sign-in and this upstream authorization are separate connections.
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
- When you connect an existing server, enter its HTTPS MCP URL and select Authenticate if prompted. For a server already in Manufact, use Authenticate in the server header.
- Complete the upstream service's OAuth flow with your test account. Continue only if the requested access fits your test setup.
- Return to the server's Overview page. Check Connection Status and the Authenticated test account shown below it.
The email comes from the upstream authorization server's UserInfo response for the current OAuth session. It identifies the account used by the dashboard; it is not your Manufact login email. If the upstream service does not expose a readable email through UserInfo, the panel shows 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, select Disconnect in the server header to clear the dashboard credentials, then Re-authenticate with the account you want. If your browser remains signed in to the old upstream account, switch accounts there before completing OAuth again.
Dashboard connection versus client traffic
The dashboard's test account is for Manufact's inspection and testing. Your users and MCP clients complete their own OAuth flows with the upstream server. The dashboard credentials are not used for traffic through the optional Manufact proxy. See Connecting clients for client setup.