Sharing a server’s sign-in, the suite Accounts setting and the run
page’s Credentials line are rolling out gradually. If you don’t see
them, they aren’t on for your account yet. Uploading tokens to your own
accounts and the
accounts field in the API and CLI are available to
everyone.Before you start
- The server is saved in a project, signs in with OAuth and, if it is remote, uses HTTPS. Shared and uploaded accounts are refused over plain HTTP; loopback development addresses are allowed.
- Use dedicated test accounts with the least access your tests need. Every project member can run as every shared account.
Share the server’s sign-in
A project admin does this once per server.1
Open the server's Auth tab
Open the server from your project and select the Auth tab.
2
Turn on Share sign-in with the project
MCPJam asks you to confirm, because members’ local apps will receive the
access tokens of the accounts admins connect here. Click Share sign-in.
3
Add the project accounts
Connect accounts here, or upload them from CI as described below. A server
holds up to 8 project accounts.
Upload each test user’s token from CI
Sign the test user in from your CI job, then upload the access token under a name you choose:--access-token-env <VAR> reads the token from an environment variable instead. The public API takes the same upload as PUT /projects/{projectId}/servers/{serverId}/accounts/test-automation-1. See Server accounts for the request body, and the CLI reference for every flag.
- Upload again under the same name to replace the token. The account keeps its ID, so suites that run as it keep doing so. Nothing checks who a token belongs to, so keep each name for one test user.
- Upload more often than the token lasts. For tokens that last an hour, upload every 30 to 45 minutes, or upload in the step right before each run. Uploads are budgeted per person and server.
- Say when the token expires.
--expires-in(tokens.expires_inin the API) is the token’s remaining lifetime in seconds. If you leave it out and the token is a JWT with anexpclaim, MCPJam stops using the token at that time. When both are present, the earlier one applies. An opaque token uploaded without--expires-inhas an unknown expiry, and MCPJam relies on the server to reject it once it expires. - Use a project admin’s API key, and only for this job. Only a project admin can upload to a project account. A dedicated key can be revoked without breaking anything else. New keys expire after 90 days unless you pick another lifetime when you create them, so renew the key before then.
Choose which account a suite runs as
1
Open the suite's settings
Open the suite’s Suite settings page.
2
Find Runs as you
Under Accounts, the Runs as you group lists each of the suite’s
servers with the accounts you can choose: your own, or on a shared server
the project’s.
3
Tick the test user's account
Tick the account for each server. To run as one test user, leave only
that account ticked. The choice saves right away.
Run locally
A member’s local Inspector, version 3.22.0 or later, receives the access token of a shared or uploaded account when the server allows local runs. Refresh tokens and client secrets stay in MCPJam. A personal server’s uploaded account is available locally only to its owner. Seecloud server-accounts set for what local delivery hands out and how to stop it.
What each run records
When a run starts, it records each account it used and the facts of its token. A later upload doesn’t change what an earlier run shows. The run page header shows Ran as (who started the run), Accounts, and a Credentials line for each account:- Uploaded or Signed in says how the token was stored, then when and by whom.
- Expires gives the token’s expiry, or Expiry unknown when nothing stated one.
- Identity comes from the server’s profile tool when it answered: its
nameornickname, and itsid. Otherwise it comes from the token’s claims:preferred_usernameas the name andsubas the subject, or the issuer (iss) when neither is present. MCPJam reads claims from a JWT without checking its signature, so it labels them “from the token”. - Email comes from the profile tool’s
email, then the token’semailclaim, then the token’ssuborpreferred_usernamewhen one of them is an email address.
Organization admins follow the same rule. Share links and guests never see an email. The API and CLI return the same record; see Which accounts a run used.
Give accounts an identity
If your tokens aren’t JWTs with useful claims, mark one tool on your server as its profile tool with"_meta": { "openai/profile": true }:
id and, optionally, name, email and nickname, all strings. Return it as structuredContent or as JSON text:
Security controls
- No browser reveals. The token of a shared or uploaded account can’t be revealed in the browser or sent to a sandbox.
- Allow local runs. A project admin can turn it off for each shared server on its Auth tab. Members’ local apps then stop receiving the accounts’ tokens from their next connection or run.
- Allow credential export. Organization owners and admins can turn it off under Organization settings → Security. MCPJam-hosted connections keep working, and local apps, the CLI, sandboxes and browser reveals are refused. It covers every saved credential in the organization, not only test accounts. Members can view the setting but can’t change it.

