Skip to main content

Remote Connector

Bolti runs a hosted MCP (Model Context Protocol) server you can add to a client as a remote connector. Instead of installing anything locally, you paste one URL, sign in through your browser, choose a workspace, and approve. The client then talks to Bolti over HTTPS and handles authentication for you.

The connector URL is:

https://mcp.bolti.co.in/mcp
Remote or local?

Use the remote connector for browser-based clients and zero-setup access (Claude web and desktop connectors, and any client that supports remote MCP servers). Use the local install when you want the server running inside your editor or CLI (Cursor, Claude Code) with a Personal Access Token. Both expose the same domain tools and permissions; local-only login_with_token and logout are omitted remotely because the HTTP session is bound to OAuth.

How sign-in works​

The remote connector uses the standard MCP OAuth 2.1 authorization flow, so you never paste a token:

  1. Your client discovers Bolti's authorization server from the connector URL.
  2. It opens a Bolti sign-in page in your browser.
  3. You sign in (the same account you use for the dashboard).
  4. A consent screen asks you to approve access and choose a workspace scope.
  5. The client receives a short-lived access token and refreshes it automatically in the background.

You stay in control: the connector only ever has your permissions, and you can revoke it at any time (see Managing access).

Add the connector​

The exact menu wording varies by client, but every flow is: find "add a custom / remote connector", paste the URL, and complete the browser sign-in.

Claude (web and desktop)​

  1. Open Settings -> Connectors (Claude web) or Settings -> Connectors / Extensions (Claude Desktop).
  2. Choose Add custom connector.
  3. Paste https://mcp.bolti.co.in/mcp and continue.
  4. A Bolti sign-in window opens. Sign in, pick the workspace scope, and click Approve.
  5. The Bolti tools appear in your tool list.

Cursor​

Cursor can connect to a remote MCP server by URL. Add this to ~/.cursor/mcp.json (global) or a project .cursor/mcp.json:

{
  "mcpServers": {
    "bolti": {
      "url": "https://mcp.bolti.co.in/mcp"
    }
  }
}

Reload Cursor. When you first use a Bolti tool, Cursor opens the browser sign-in and consent screen, then remembers the connection.

Any other client​

Any client that supports remote MCP servers over HTTPS with OAuth can connect. Point it at https://mcp.bolti.co.in/mcp; it will discover the authorization server and run the sign-in flow. No manual token or configuration is required.

Client support varies

Not every MCP client supports remote connectors yet. If yours only supports local servers, use the local install with a Personal Access Token instead - it exposes the same tools.

When you approve a connector, Bolti asks how much access to grant:

ChoiceWhat the connector can reach
All my workspacesEvery workspace you are a member of, with your role in each.
A specific workspaceOnly that one workspace. The connection cannot touch any other.

Pick the narrowest scope that fits what you are doing. You can always remove the connection and reconnect with a different scope later.

Permissions and safety​

  • The connector acts as you. It can never do anything your own account cannot, and workspace-scoped grants are enforced by the Bolti backend on every call.
  • Read and write tools are separate. Clients may show confirmation prompts for destructive or billed actions. Regardless of client behavior, Bolti still enforces your workspace role, permissions, rate limits, and credit checks on every request.
  • Secrets are never exposed. Tool credentials and SIP passwords are write-only; read tools return them masked.

See the tool catalog for exactly what each tool does and which ones require confirmation.

Managing access​

Each connector you approve issues access under your account. To review or revoke it:

  1. Open the Bolti dashboard.
  2. Go to profile (bottom-left of the sidebar) -> Access Tokens.
  3. Connector grants are listed with an oauth: prefix. Click Revoke to immediately cut off that connector.

Revoking takes effect right away. To reconnect, remove the connector in your client and add it again.

Revoke when you stop using a client

If you remove a connector from a client, also revoke its grant in Access Tokens so no refreshable session is left behind.

Troubleshooting​

SymptomFix
Sign-in window never returns / loopsMake sure you completed sign-in and clicked Approve. Pop-up blockers can interrupt the redirect; allow pop-ups for the client and retry.
Connected to the wrong workspaceRemove the connector in your client and re-add it, choosing the correct workspace on the consent screen.
Tools stopped working after a whileThe grant may have been revoked, or the account lost access to the scoped workspace. Re-add the connector.
Your client does not support remote connectorsUse the local install with a Personal Access Token.

Self-hosting​

Enterprise and on-premise customers can run the remote MCP server themselves and point clients at their own URL instead of https://mcp.bolti.co.in/mcp. The connector behaves identically. Talk to your Bolti contact if you need this.

Where to go next​

If you want to...Read
Install locally with a token insteadInstallation
See every tool the connector exposesAvailable Tools
Understand tokens, scopes, and revocationPersonal Access Tokens
Get inspired with concrete promptsUse Cases