Repository navigation
Add Vercel container configuration - #1
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
What changed
Dockerfile.vercelat the repository rootpython:3.11-slimuvgoogle-ads-mcpentry pointWhy
Vercel container deployments detect
Dockerfile.vercel. The existing MCP server already reads the platform-providedPORTand binds to0.0.0.0when OAuth is configured, so no Python server changes are needed.Impact
This PR only prepares the repository for phase 7. It does not create a Vercel project, configure secrets, or deploy anything.
Validation
docker build --file Dockerfile.vercel --tag converted-google-ads-mcp:phase7 .["google-ads-mcp"]/mcpreturned401, confirming OAuth protection200Known upstream dependency issue
The unbounded upstream dependency
fastmcp>=3.2.0currently resolves to FastMCP4.0.0b3in a fresh container build. This is not introduced by this Dockerfile, but it can cause the existing golden smoke test to fail. Keep this PR in draft and do not merge until the required CI checks are green or the upstream dependency drift is addressed separately.