Manage connected clients

Once you’ve connected a Claude client to Moonjar via MCP, the connection sticks until you revoke it. This page is how to see what’s connected and cut access when you need to.

Before you start

At least one Claude client connected. See Connect Moonjar to Claude for the initial pairing.

See connected clients

Open the Moonjar app.
Go to Settings → Connected apps (or the equivalent path surfacing the MCP-OAuth client list — [TODO: VERIFY exact menu path on mobile]).
The screen lists every Claude client that’s registered against your account: the client name, when it first connected, and when it last made a request.

Revoke a client

Tap the client.
Tap Revoke.

The client’s tokens are invalidated immediately. The next request the client makes — a tool call, a token refresh — fails. Most Claude clients respond by prompting you to re-authenticate; if you don’t want it back, ignore the prompt and remove the connector from the Claude side too.

Revoking only affects that client. Other Claude clients you’ve connected stay connected.

Revoke from Claude’s side

Removing the MCP connector inside Claude (Claude.ai workspace settings, Claude Desktop connectors, Claude Code MCP list) stops that client from talking to Moonjar going forward. The OAuth tokens Moonjar issued to that client remain on Moonjar’s side until they expire on their own (1 hour for access, 30 days for refresh).

For complete removal, do both: revoke on Moonjar, and remove the connector on Claude’s side.

What happens to the chat history

Revoking a Claude client doesn’t touch any chats you had with that client. Those live in Claude — not in Moonjar — and they stay there. Anything Claude captured into Moonjar via the write scope (URLs you saved, items you added to collections, reminders you created) stays in your Moonjar library.

Token lifetimes for reference

Access tokens — 1 hour. The client refreshes silently in the background.
Refresh tokens — 30 days. After 30 days of inactivity, the client has to re-authenticate from scratch. Refreshing a token rotates the refresh token (one-time-use), so old refresh tokens stop working as soon as a new one is issued.