Checking your Marqii MCP connection and switching users

Applies to: the Marqii connector (MCP) in Claude, ChatGPT, Cursor, Windsurf, Continue, and other MCP clients.

When you connect Marqii to an AI assistant, the assistant signs in as you and keeps that sign-in until it expires or you sign out. This article covers three things:

1. How to check whether your connection is healthy and when it expires

2. How to sign in as a different Marqii user

3. How to sign out manually if the normal steps don't work

1. Check your connection status

Ask your assistant, in plain language:

Check my Marqii auth status.

The assistant runs the marqii_auth_status tool. It takes no input, touches none of your business data, and answers with something like this:

{
  "accountId": "4821",
  "cognitoUsername": "you@yourcompany.com",
  "authorized": true,
  "expiresAt": "2026-11-04T18:22:07.000Z",
  "daysRemaining": 76,
  "renewalRecommended": false,
  "message": "Authorized and healthy."
}

Other phrasings that work: "Is my Marqii connection still valid?", "When does my Marqii connection expire?", "Which Marqii account am I connected as?"

How to read the answer

When authorized is false, reason tells you why:

Two answers you may see instead:

• "sessionType": "forwarded" — you're using the chat assistant inside the Marqii dashboard, not an external connector. That chat rides on your live dashboard session, so it has no separate expiry. If it stops working, refresh the dashboard and sign in again.

• "expiresAt": null — the connection predates our expiry tracking. It still works; the expiry date gets recorded the next time you reconnect.

Expiry is not something the assistant can fix

The assistant cannot renew its own Marqii sign-in. Renewal always needs a person to complete the browser sign-in once. If you run scheduled or unattended work through the Marqii connector, check marqii_auth_status periodically and act when renewalRecommended turns true — otherwise those runs will start failing with an authorization error.

Reconnecting

The wording varies by client, but the shape is the same everywhere:

A browser tab opens, you sign in to Marqii, and the tab redirects back. That's the whole flow.

2. Sign in as a different Marqii user

Here's the part that surprises people: disconnecting and reconnecting is usually not enough.

Marqii sign-in keeps a session cookie in your browser. When you reconnect, the sign-in page sees that cookie and logs you straight back in as the same person — often with no login form at all. To switch users, you have to clear that cookie as well.

The reliable sequence

1. Disconnect the Marqii connector in your assistant (see the table above).

2. Open the sign-out link in the same browser you sign in to Marqii with:

   https://mcp.marqii.com/logout

   You should land on a page that says "You're signed out."

3. Reconnect the connector. You'll now get a real login prompt. Sign in as the other user.

4. Confirm it worked: ask the assistant to "check my Marqii auth status" and check that cognitoUsername and accountId are the ones you expect.

Step 2 is the step people skip. If you reconnect and it silently logs you back in as the previous user, either you skipped it, or you opened the link in a different browser than the one your assistant used for sign-in.

Alternative: use a private window

If you'd rather not sign out of Marqii in your main browser, do the reconnect from a private / incognito window. That window has no Marqii cookie, so it always prompts for credentials. Some assistants let you choose which browser handles sign-in; others always use your default browser, in which case use the sign-out link instead.

What signing out does and doesn't affect

• It's per connector. Signing out of Claude's Marqii connector does not sign you out of Cursor, ChatGPT, the Marqii dashboard, or anybody else's connector. Each one holds its own sign-in.

• It changes nothing in your Marqii account. No data, settings, or users are modified. You can reconnect whenever you like.

• Allow up to an hour for it to take full effect. For a short window after signing out, a connection that is already warm may still complete a Marqii request. That's expected. If you need an old sign-in to stop working immediately — someone left the company, for example — contact Marqii support and ask for that account user to be disabled, which takes effect at once.

3. Manual sign-out URL (fallback)

If https://mcp.marqii.com/logout won't load, or your browser blocks the redirect, go to the sign-in service directly. Copy this into your address bar exactly as written, as one unbroken line:

https://auth.marqii.com/logout?client_id=6egkb366slmq13intqm7bjq5sp&logout_uri=https://mcp.marqii.com/logout/complete

It clears the Marqii sign-in cookie and returns you to the same "You're signed out" confirmation page.

Notes on the manual link

• Open it in the browser you actually sign in to Marqii with. Cookies are per browser and per profile; a link opened elsewhere clears a cookie that was never the problem.

• It clears the browser cookie only. It does not disconnect the connector inside your assistant. Use the manual link and disconnect/reconnect in the assistant — otherwise the assistant may keep using the sign-in it already has.

• Don't edit the link. The client_id and logout_uri values have to match exactly; changing either one produces an error page instead of signing you out.

• If you land on an error page, the most likely cause is a truncated or line-wrapped URL. Copy it again as a single line.

Which link should I use?

4. The marqii_switch_user tool

Your connector also exposes a marqii_switch_user tool. Ask:

Sign me out of Marqii.

It clears the stored Marqii sign-in for that connector and hands back a logoutUrl to open in your browser:

{
  "status": "signed_out",
  "message": "Server-side Cognito session cleared. Open the logoutUrl in a browser to also clear the Cognito hosted-UI cookie, then disconnect and reconnect the Marqii connector to sign in as another user.",
  "logoutUrl": "https://mcp.marqii.com/logout"
}

You still have to open that URL and then reconnect the connector — the tool handles the server-side half only. If you would rather not use the tool, the steps in sections 2 and 3 accomplish the same thing.

Troubleshooting

Still stuck?

Contact Marqii support with:

• the full marqii_auth_status output,

• which assistant and client you're using,

• and the time (with timezone) the problem last happened.

Those three details are enough for us to trace your connection in our logs.