Connect other AI assistants

Finsplore Connect will work with any assistant that supports remote MCP servers over HTTP. This article covers the ones we checked against their own documentation, then the general steps for any other.

Each assistant's menus and options belong to its maker and can change. If a step does not match, use the maker's article linked in each section.

Before you startCopy Anchor Link

• Check that Connect shows in your Finsplore menu, under Assistant.
• The address you will use is: https://api.finsplore.io/mcp (available when Finsplore Connect launches)
• Assistants that sign in through your browser need you to approve access in Finsplore. Assistants that use an access token need you to create one first.

Gemini CLICopy Anchor Link

Gemini CLI supports remote HTTP servers and sign-in through your browser. See Gemini CLI's MCP server documentation.

1. Run:

   Copy Text

   gemini mcp add --transport http finsplore https://api.finsplore.io/mcp

   This address works once Finsplore Connect launches.

2. In Gemini CLI, run /mcp auth finsplore and sign in to Finsplore in your browser.

Signing in this way needs a browser on the same computer, so it does not work over a remote SSH session. In that case, use an access token with the --header option instead.

PerplexityCopy Anchor Link

Perplexity can add a custom remote connector. An admin may need to allow this first on an organisation account. See Perplexity's article on custom remote connectors.

1. Go to Customize and then Connectors.
2. Choose Custom connector, then Add MCP connector.
3. Enter a Name, such as Finsplore, and paste the address above as the MCP Server URL.
4. Choose Advanced (OAuth) for authentication.
5. Tick the box to confirm you understand the risks of custom connectors, then click Add.
6. Adding does not connect it. Click + on the connector card to connect.
7. Finsplore opens in your browser. Sign in if you are asked to, then approve access.

Finsplore's approval screen may label Perplexity as an unverified app for now. This is expected, and you can go ahead if you started the connection yourself.

VS Code with GitHub CopilotCopy Anchor Link

VS Code can use remote MCP servers in agent mode. See VS Code's MCP servers article.

1. Run MCP: Add Server from the Command Palette.
2. Choose HTTP, then paste the address above.
3. Enter a name, such as finsplore, and choose where to save the configuration.

You can also edit .vscode/mcp.json yourself:

{
  "servers": {
    "finsplore": {
      "type": "http",
      "url": "https://api.finsplore.io/mcp"
    }
  }
}

This address works once Finsplore Connect launches.

VS Code's article does not describe signing in through the browser for HTTP servers. If VS Code does not offer to sign you in, use an access token. Your organisation may also limit which MCP servers Copilot can use.

CursorCopy Anchor Link

Cursor supports remote MCP servers, including sign-in through your browser. See Cursor's MCP documentation.

1. Open .cursor/mcp.json in your project, or ~/.cursor/mcp.json to make Finsplore available in every project. Create the file if it does not exist.

2. Add Finsplore:

   Copy Text

   {
     "mcpServers": {
       "finsplore": {
         "url": "https://api.finsplore.io/mcp"
       }
     }
   }

   This address works once Finsplore Connect launches.

3. Cursor asks you to sign in to Finsplore. Approve access in your browser.

To use an access token instead, add a headers entry with "Authorization": "Bearer ${env:FINSPLORE_TOKEN}" and keep the token in an environment variable named FINSPLORE_TOKEN.

CodexCopy Anchor Link

Codex supports remote servers and sign-in through your browser. See OpenAI's Codex MCP documentation.

1. Run this command:

   Copy Text

   codex mcp add finsplore --url https://api.finsplore.io/mcp

   This address works once Finsplore Connect launches.

2. Run codex mcp login finsplore. Codex opens your browser so you can sign in to Finsplore.

3. Finsplore asks you to approve Connect Codex. Choose what Codex may do, then click Approve.

Finsplore's approval screen labels Codex as an unverified app, because it comes back to your own computer, and Connect lists it as Unverified too. This is expected, and you can go ahead if you started the connection yourself and the address at the bottom is 127.0.0.1 or localhost.

If your browser does not open, for example on a remote computer, run codex mcp login finsplore --no-browser instead. Codex prints an address to open on the same computer that runs Codex.

To use an access token instead, add --bearer-token-env-var FINSPLORE_TOKEN to the codex mcp add command, and keep the token in an environment variable of that name.

Any other assistantCopy Anchor Link

If your assistant supports remote MCP servers over HTTP (called Streamable HTTP):

1. Add a new remote or custom MCP server.
2. Enter the address above.
3. Choose OAuth for authentication if the assistant asks. Most assistants find Finsplore's sign-in details by themselves.
4. Sign in to Finsplore and approve access when your browser opens.

If the assistant cannot sign in through a browser, it may let you add a header. Use an access token as an Authorization: Bearer header.

Related articlesCopy Anchor Link

• Create an access token
• See activity and disconnect an assistant
• Fix problems connecting an assistant