Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Sign in to an MCP server
Skills, MCP and API

Sign in to an MCP server

Remote MCP servers can require your authorization before Chetty may call their tools; this page covers that sign-in and the way back.

Check the sign-in state

Open the server's detail on the MCP page. Its authentication state is separate from its connection state:

  • No sign-in required: the server accepts calls without authorization.
  • Signed in: the stored authorization is in use.
  • Sign-in needed: the server wants authorization, or a previous request expired.
  • Sign-in error: the last sign-in attempt failed.
  • Unsupported transport: a legacy server that cannot connect at all.

When the server reports them, the required permissions appear under Permissions.

Sign in

  1. Select Sign in in the server's detail.
  2. Chetty opens the server's authorization page in a new tab.
  3. Approve the access there. Being on that page does not mean you are signed in.
  4. Return to Chetty and refresh the status in the server's detail.

A sign-in request expires after 10 minutes; start a new one instead of waiting. The buttons are disabled while a request is running.

Finish in the new tab

After you approve, the provider sends you back to the MCP callback page, which confirms the result and returns you to MCP.

Chetty removes the authorization code from the address bar immediately, confirms the result once and replaces that entry in the browser history, so Back cannot submit it again. A missing, invalid, expired or denied request shows a specific message with Back to MCP.

If you were signed out of Chetty when you came back, sign in with the same account that started the authorization. A password login keeps the callback address, and a successful Microsoft single sign-on returns to it. The server still checks the account and the one-time request before it accepts the authorization.

If sign-in fails

  • The new tab does not open: allow new tabs for this site and select Sign in again.
  • The message says the request expired: start a new sign-in from MCP.
  • The authorization was denied: the credentials stay unset; start again from MCP if you want to approve it.
  • The callback shows a general failure: a network failure or an unexpected answer gives that message without server details. Do not reload or resubmit it; start a new sign-in from MCP.
  • The status stays at Sign-in needed: complete the authorization in the tab and refresh the status in the detail.

Sign out

Select Sign out to remove the stored authorization. The credentials stay in the server's ownership scope and are never shown in the browser. A refused request remains visible in the detail instead of disappearing.

Replace a legacy SSE server

A legacy SSE server stays visible as Unsupported transport and cannot be enabled or reconnected. Chetty does not migrate its address on its own.

  1. Open the server's detail.
  2. Select Streamable HTTP as the transport.
  3. Enter the server's streamable HTTP address.
  4. Select Save. It stays disabled until a supported transport is chosen.

See Connect tools through MCP for adding a server, Manage MCP servers for ownership and reconnecting, and MCP Connector Plugin for the reference.