Changes to support Vercel deployment - #293
Open
TheDistanceHQ wants to merge 10 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
I have not been able to get the MCP to work when hosted using Vercel. I believe its down to the hash routing.
Claude Desktop would just display an error after "Connecting" the MCP
Solution
This is the outcome of some vibe coding with Cursor to resolve the issue.
I'm not expecting you to accept this pull request, but I thought I'd raise it so you can review the changes I had to make as it might help understand the problems I had with the Vercel deployment and the MCP.