Vercel Connect's 90+ Preset Connectors Turn MCP Setup Into Catalog Work

Vercel's new preset connectors matter because they change the starting shape of integration work.

The headline number is easy to repeat: 90-plus services now have presets in Vercel Connect. But the more useful operator read is that Vercel is trying to stop common connector setup from starting as a blank page every time.

According to Vercel's July 21 changelog, preset connectors pre-populate the brand name, icon, auth type, and the MCP or discovery URL for supported services like Shopify, Resend, Sanity, Okta, Workday, and Jira. That sounds small until you remember how much integration friction comes from re-entering the same known metadata and then checking whether the connector shape is even right.

Vercel is not pretending the whole job is solved. The company explicitly says preset connectors are not managed connectors. They do not register your app with the external service for you, and you still have to add the credentials each service requires. That distinction matters. The real improvement is not that policy disappears. It is that the repetitive setup scaffolding gets lighter.

That is useful because agent and workflow systems increasingly depend on lots of connectors that all need a recognizable auth story. When every integration begins with hand-entered labels, discovery URLs, and auth choices, teams waste time on shape work before they even reach the real access decision. A preset directory turns more of that into catalog selection.

The CLI angle makes this more than dashboard polish. Vercel says you can start with vercel connect create and vercel connect attach today, even though full CLI support for preset connectors is still coming. That means the lane is already moving toward repeatable attachment workflows rather than one-off clicking.

Butler's read is that this matters most for teams treating MCP-style and service-connected workflows as operating surfaces. The win is not more connectors exist. The win is that setup begins to look like choosing a known pattern, reviewing the security details, and moving on faster.

Related coverage

• the earlier Vercel Connect scoped-token article
• the Vercel MCP and CLI operator-loop piece
• the Vercel AI Gateway routing article

AI Disclosure

This article was researched and drafted with AI assistance, then reviewed and edited for clarity, accuracy, and editorial quality.