Skip to content
All tool news

Tool desk · Updated daily

Tool news·Vercel·

Vercel Adds Submit_feedback to Its MCP.

Vercel adds submitfeedback to its MCP, letting agents send bug reports, friction reports and feature requests with structured context.

CW

Create With tool desk

3 sources checked · 2 min read · 2 sections

ShareLinkedIn
Vercel Adds Submit_feedback to Its MCP

submit_feedback is a new Vercel MCP tool that lets agents and harnesses send bug reports, friction reports and feature requests directly to the Vercel team. Feedback can include structured context about the task being attempted, the expected behaviour and what happened instead.

The Vercel changelog describes a plain-language workflow. A user can ask their agent to report that a deployment error failed to identify a missing environment variable, for example. The agent can then prepare and submit that report without switching to a separate feedback form.

It covers three types of feedback: bugs, points of friction and feature requests. Reports originate inside the agent or harness already working with Vercel MCP, so the submission can carry details from the task where the issue appeared.

How submit_feedback packages the problem

Feedback begins with a message explaining the issue. The agent can attach a structured context object containing the tool involved, the task being performed, the result the user expected and the result they received.

In Vercel’s example, the task is deploying a preview. The expected result is an error that identifies the missing environment variable. The actual result is an error that does not name it. That turns a general complaint about deployment errors into a report tied to a specific action and outcome.

The same structure applies to feature requests and friction reports. An agent or harness can submit the request itself, while attaching the context available from its current run. This preserves both the user’s plain-English account and the operational details describing where the problem occurred.

The tool requires the user to sign in. It only sends feedback when the user explicitly requests it, rather than automatically reporting activity from an agent session.

Vercel positions the tool as a direct feedback route from agent-driven work. It sits inside Vercel MCP, alongside the tools an agent or harness uses to carry out its task.

Frequently asked questions

What is Vercel submit_feedback?

submit_feedback is a Vercel MCP tool for sending bugs, friction reports and feature requests from an agent or harness. It can attach structured details about the task, expected behaviour and actual result.

Which Vercel plan includes submit_feedback?

The changelog says submit_feedback is now included in Vercel MCP. It does not give plan or pricing details.

Does submit_feedback send reports automatically?

No. The tool only sends feedback when the user explicitly asks the agent to do so, and the user must be signed in.

Sources

3 checked

How we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.

Worth passing on?

ShareLinkedIn

Go deeper on Vercel

Related reading, watching and going.

Everything on Vercel →

The briefing

19 May 2026

How to Migrate Your App from Lovable to Claude Code in 2025

Step-by-step guide to migrating your Lovable app to Claude Code. Learn how to move from Lovable's managed platform to a stack you own and control.

Read →

The briefing

10 Feb 2026

OpenClaw Review: 2 Weeks With This AI Agent

Honest 2-week review of OpenClaw — an autonomous AI agent powered by Claude. We test setup, safety, autonomy, and real value to see if it's worth using.

Read →
34 min

Podcast

My Daughter Built a Website Business, Claude Design First Look & Going All-In on Cloudflare

James and Kieran discuss practical AI-powered development through real-world examples, including a seven-year-old building a website business with Claude Code voice mode, Anthropic's new Claude Design tool, API security challenges in the AI agent era, and Cloudflare's expanding AI infrastructure offerings. The episode covers hands-on experiences with vibe coding, emerging design tools, and the evolving landscape of AI-assisted development.

Watch now ↗

Podcast

53. Why Your Vibe Code Needs Tests, Ditching SaaS & AI Agents That Work While You Sleep

James and Kieran discuss the practical realities of building AI-powered software, emphasizing the importance of testing in vibe-coded applications, exploring alternatives to traditional SaaS tools, and implementing autonomous AI agents for business operations. The episode covers technical topics like Convex databases, app store bottlenecks from AI-generated submissions, and using OpenClaw as a marketing automation agent.

Watch now ↗
38 min

Podcast

52. Your AI Co-Founder: OpenClaw, Manus & the Zero-Person Business

In this Create With podcast episode, James and Kieran are joined by Matt Roberts from Happy Operators for an in-depth discussion on using autonomous AI agents in production. The conversation covers practical experiences with OpenClaw, security considerations, comparison with emerging tools like Manus, and the broader shift toward AI-assisted development. They also discuss the VibeCoding Olympics results, Bubble's new AI capabilities, and research on Claude.MD file effectiveness.

Watch now ↗

Latest tool news

What else changed this week.

All tool news
VercelDigest

What Vercel Shipped in Late October

Vercel shipped quicker static deployments, four AI Gateway models, more free domain choices and new CLI controls in late October. The changes cover developers testing sites…

The Create With Briefing

Don't watch forty changelogs. Read one email.

Every Tuesday: the tool changes worth knowing, real business use cases, and what's on near you. Free, unsubscribe any time.