Before you start
You’ll need two things:- A paid Claude plan. Custom connectors are available on Claude Pro, Max, Team, and Enterprise, not the free tier.
- A Fruit Stand API key. If you don’t have one yet, grab a free key below. If you already have an account, open your dashboard to copy it.
Get a free API key
New to Fruit Stand? Our pricing page has a free tier that’s enough to get started — no card required.
View your API keys
Already have an account? Copy your API key from your subscriptions dashboard.
Step 1: Open the custom connector dialog
In the Claude Desktop app, go to Settings → Connectors, scroll to the bottom, and click Add custom connector.Step 2: Name the connector and enter the server URL
Give the connector a name you’ll recognize in your connectors list, then enter the Fruit Stand MCP server URL:
Name the connector and paste the Fruit Stand MCP server URL.
Step 3: Set authentication to None and add your API key header
On the next screen, under Authentication, select None — the server uses an API key rather than OAuth. Then, under Request headers, add one header:- Header name:
authorization - Value: your API key, prefixed with
Bearer(see the warning below) - Leave Required checked.

Select None for authentication, then add an 'authorization' header set to 'Bearer '.
Step 4: Confirm the connection and tools
Back on the Connectors page, the connector shows as connected with its tools listed under Tool permissions. You’ll see the Fund Returns tools —SearchFunds, GetFund, GetTrailingReturns, GetCalendarReturns, BatchTrailingReturns, and BatchCalendarReturns. Set them to Always allow (or leave them to prompt) depending on how much you want Claude to ask first.

Once connected, the Fund Returns tools appear under Tool permissions.
Step 5: Try it out
Start a new chat and ask something the data can answer, for example:Search for funds matching “total stock market” and show me the 1-, 5-, and 10-year trailing returns for the closest match.Claude will call the Fruit Stand tools and answer from live data.
Troubleshooting
The connector fails to authenticate
The connector fails to authenticate
Nearly always the
Bearer prefix. Re-open the connector’s request header and confirm the value is Bearer + a single space + your key, with no extra spaces before or after. Because the value is hidden after saving, the quickest fix is to delete the header and re-add it.I don't see 'Add custom connector'
I don't see 'Add custom connector'
Custom connectors require a paid Claude plan (Pro, Max, Team, or Enterprise). On the free tier the option isn’t shown.
Where do I find my API key?
Where do I find my API key?
Open your subscriptions dashboard to view and copy your key. Need one? Start free on the pricing page.