Repository navigation
fix(evi): re-allowlist the vercel mcp to its renamed tools - #709
Closed
evlogai[bot] wants to merge 1 commit into
Closed
evlogai[bot] wants to merge 1 commit into
evlogai[bot] wants to merge 1 commit into
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
commit: |
This was referenced Sep 18, 2026
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
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
The Vercel MCP server renamed its generic endpoint pair again.
apps/evi/agent/connections/vercel.tsallowlistssearch_vercel_endpointsandcall_vercel_endpoint(added in 878bdd3), but the server no longer serves tools under those names: the tools reference (last updated 2026-09-15) now exposes dedicated named tools and lists no search/call endpoint pair. Evi's live session confirms it: the connection description interpolated from that commit is served, the two allowlisted tools are not.This re-allowlists the connection to the current read-only tool surface:
list_teams,list_projects,get_projectlist_deployments,get_deployment,get_deployment_build_logsget_runtime_logs,get_runtime_errors(unchanged)get_web_analyticslist_agent_run_projects,list_agent_runs(unchanged)get_deployment_build_logsis the payoff: with it, Evi can read the build output of a failed production deploy (dpl_H6tPefeCSABrVarxrsorS4BCDCYB is the current one) without asking for a dashboard paste.Deliberately not allowlisted, kept as-is from the current posture:
deploy_to_verceland the purchase/domain tools: the connection is read-only.get_agent_run/get_agent_run_trace: per-run content stays out of scope, run-level metadata only, per the PostHog rule inapps/evi/AGENTS.md.The connection instructions moved from the "search the endpoint, then call it" paragraph to the dedicated tools, and the daily-digest skill's visitors step now names
vercel__get_web_analyticsinstead of the REST path it can no longer call.Checks
pnpm --filter evi typecheck(tsc): passpnpm run lint --filter=evi: passeslint apps/evi/agent/connections/vercel.ts: passNot verifiable here: that the MCP server actually serves these tool names can only be confirmed on a deployed connection. Once this ships,
vercel__get_deployment_build_logson the failed prod deploy is the first thing to try.No changeset:
apps/*only.