Perplexity, Le Chat and Goose
Connect other AI apps that support custom connectors.
Tahoe works with any AI app that can add a remote MCP server with sign-in. This page has the steps for Perplexity, Mistral Le Chat and Goose, and what to look for in any other app.
You need a paid Tahoe plan, and AI apps must be allowed in your workspace (they are by default). Connect your AI app explains the Tahoe sign-in page.
Perplexity
Custom connectors are a paid feature in Perplexity. On Enterprise plans, an admin can switch them off.
- Open Settings → Connectors and click Add custom connector.
- Enter the URL
https://mcp.hiretahoe.com/mcp. Sign in to Tahoe when asked, choose your workspace and click Allow. Then save the connector. - Switch the Tahoe connector on in each thread where you want to use it.
Mistral Le Chat
You need administrator access to your Le Chat account. On Free, Pro and Student plans, the account owner is the administrator.
- Open Connectors, click + Add Connector and choose Custom MCP Connector.
- Enter the name
tahoeand the server URLhttps://mcp.hiretahoe.com/mcp. Le Chat detects that Tahoe uses a sign-in. - Sign in to Tahoe, choose your workspace and click Allow.
In My Connectors, you can set each Tahoe tool to Always allow or to ask you every time.
Goose
In the desktop app: open Extensions, click Add custom extension and fill in:
| Field | Value |
|---|---|
| Type | Streamable HTTP |
| Name | tahoe |
| Endpoint | https://mcp.hiretahoe.com/mcp |
In the terminal: run the command below, choose Add Extension, then Remote Extension (Streamable HTTP), and enter the same values.
goose configureGoose opens the Tahoe sign-in the first time it runs a Tahoe tool.
Any other app
If your app can add a remote MCP server over Streamable HTTP with OAuth sign-in, it can use Tahoe. Look in its settings for a custom connector, MCP server, integration or extension, and give it the server address. The app finds Tahoe’s sign-in on its own.
| If the app asks for | Enter |
|---|---|
| Server URL or endpoint | https://mcp.hiretahoe.com/mcp |
| Transport or type | Streamable HTTP (some apps just say HTTP) |
| Authentication | OAuth. Many apps detect this on their own. |
- Apps that only run servers on your own computer (sometimes called local or stdio servers) cannot connect to Tahoe.
- Apps that ask for a client ID and secret need an app registered by your workspace. A Tahoe owner or admin can create one in Settings → AI connectors → Registered apps by choosing Internal agent. The steps match those for Gemini Enterprise.
- Connecting your own software, with no person signing in? A Tahoe MCP connection always belongs to one person and is meant for working in a chat. For a system that talks to Tahoe on its own, use the Tahoe API.
How many credits do we have left, and what did we spend them on this week?
A recruiter at Kestrel Labs asks this in Le Chat before starting a large search. Le Chat reads the balance and this week’s credit use from Tahoe, such as search pages and contact details found. Checking credits is free.