Connect over a decade of HFS research directly to your AI client in a few clicks. Ask questions and get answers grounded in HFS research, with citations, right in the AI tool you already use. Available now for Claude and ChatGPT; with Gemini support in beta.
This feature is available exclusively to active HFS Research members
You must have an active membership to connect HFS Research's MCP to an AI client. Please reach out to our sales team to discuss options.
Confirm these prerequisites, then setting up the connection only requires a couple of clicks.
You must have an active Strategic or Elite HFS Research membership.
Your IT administrator must enable MCP access company-wide before your AI tool profile can access the HFS MCP.
Use the most recent version of Claude, which supports MCP connectors. ChatGPT MCP support is currently in beta, and Gemini support is planned for future releases.
Pick the platform you use most. Each guide walks through the connection flow with screenshots and provides the exact endpoint URL and what to expect from the OAuth login.
The instructions for the Claude Desktop application config file follow at the bottom of the section.
Click on the Customize option on the top left-hand side.
In the Customize window, click on Connectors, then select the + and choose “Add custom connector”
In the “Add custom connector” window, fill in two fields as below. You can copy the URL straight from the code block provided.
https://mcp.hfsresearch.com/mcp
Click Add. Claude will open a new browser tab and redirect you to the HFS MCP login page. Enter your HFS login credentials to sign in.
Return to Claude: After signing in, you’ll be redirected straight back to Claude. The HFS Research connector will now appear in the Connectors menu. When you click on the connector your will be able to adjust permissions.
Confirm HFS Research is switched on: Open a new Chat. Click the + icon to the bottom left of the chat box, hover over “Connectors”, and check that the HFS Research toggle is switched on. If it’s off, switch it on so Claude can use it for future questions about research on our website.
Start a new conversation with Claude. The HFS Research tool icon will appear in the message bar. Ask any business question and Claude will route relevant queries through HFS, and you’ll see citation links back to the source PDF on hfsresearch.com directly inside the response.
OpenAI’s support for remote MCP servers is rolling out across Plus, Team, and Enterprise plans. Exact menu paths vary by ChatGPT release channel and account type. Custom connectors on Team and Enterprise plans typically require workspace admin approval; confirm with your IT team before starting
Sign in to your ChatGPT portal. Click your profile avatar in the bottom-left and choose Settings.
Create a New App: In your ChatGPT workspace’s Apps panel (Team and Enterprise admins use the path chatgpt.com/admin/apps), click + Create. In the New App dialog, fill in:
HFS Research (or your preferred label)https://mcp.hfsresearch.com/mcp
When you hit Create, ChatGPT doesn’t switch the app on right away — it saves it as a draft. At this point only you (the admin who created it) can see it. Your teammates won’t find the HFS Research tool in their chats yet.
Publish it to your workspace (Team and Enterprise admins only). Go back to Settings → Apps and open HFS Research — it’ll have a Draft label. Click Publish button. Before it goes live, ChatGPT asks you to review two standard risk notices:
Once both are acknowledged, confirm and the label flips from Draft to Published. Your team can now see the tool — they may just need to refresh ChatGPT once.
Sign in to HFS: Once you’ve published, the connector is ready to use right away. The first time you (or any teammate) actually uses it, ChatGPT opens a new browser tab and takes you to the HFS sign-in page.
Start a new conversation with ChatGPT. The HFS Research tool icon will appear in the message bar. Ask any business question and ChatGPT will route relevant queries through HFS, and you’ll see citation links back to the source PDF on hfsresearch.com directly inside the response.
The connector fails fast and tells you why. Here are the most common situations and what they mean.
Someone signed in with your credentials on another device or AI client. HFS uses last-login-wins enforcement, so your previous session was invalidated. (Note: switching between Claude and ChatGPT on the same account also triggers this — they take turns.) Reconnect from your AI client settings and sign in again. If you didn't authorize that sign-in, change your HFS password immediately.
Your HFS account is valid, but you don't currently have MCP access — either the MCP access toggle on your WordPress profile isn't enabled, or your HFS membership has lapsed/expired. Ask your HFS administrator to enable the MCP access checkbox, or confirm your membership is active.
The AI client attempted dynamic registration but the request was blocked or returned an unexpected response. This is commonly caused by Cloudflare bot protection on OAuth endpoints.
This is usually caused by an incorrect endpoint URL.
https://mcp.hfsresearch.com/mcp
Ensure there are no extra spaces, missing paths, or trailing slashes.
The research index returned no matches for your query. Try broader keywords or alternative search phrases.
Your AI client connected to the wrong environment (e.g. a dev vs production sign-in), so the token it holds doesn't match the server's signing key. Fully remove and re-add the connector so it re-registers against https://mcp.hfsresearch.com/mcp, then sign in again.
4. Frequently Asked
Yes. The HFS MCP connector is only available to active HFS Research memberships whose accounts have MCP access enabled by their administrator.
No. The connecter only returns short text excerpts with citations. The full library is available on the HFS website. You can follow the citation link and download a report if it’s accessible to your membership.
No. HFS Research subscriptions are assigned per individual user. The connector supports only one active session at a time.
The connector uses OAuth 2.1 with PKCE, TLS 1.2+ encryption, and AWS KMS-managed encryption at rest.
Only your query and signed identity token are transmitted securely.
Your existing SSO federation will continue working normally using the same identity provider.
Any MCP-compliant client should work using the same endpoint URL.
https://mcp.hfsresearch.com/mcp
Our support team helps members navigate technical issues, onboarding, and AI client connectivity without slowing down productivity.
If you don't have an account, Register here |
With the exception of our Horizons reports, most of our research is available for free on our website. Sign up for a free account and start realizing the power of insights now.
Our premium subscription gives enterprise clients access to our complete library of proprietary research, direct access to our industry analysts, and other benefits.
Contact us at [email protected] for more information on premium access.
