# Vercel integration

By Steven Van · 2026-10-14

Workspace owners and admins can give chosen Vercel projects a hosted MCP URL and token, either per project or per person through Vercel Connect.

Graphify now has a Vercel integration, listed on the Vercel Marketplace and available as a connector on Vercel Connect. A workspace owner or admin links an existing [Graphify](<https://creatorstoolbox.com/resources/graphify>) workspace to chosen Vercel projects, and each project gets a URL and token for Graphify's hosted MCP server. The [announcement](<https://graphify.com/blog/vercel-integration>) says that server answers from an indexed repository: a definition, the callers of a function, its dependencies, what a change reaches, and saved repository knowledge. Answers include file and line references.

## Connecting a project

- Open Graphify for Vercel, select **Connect Account** and authorize the existing Graphify workspace.

- Select the projects that should receive access. Production is selected by default, and Preview is optional.

- The integration adds two variables to each chosen project: GRAPHIFY\_MCP\_URL, the hosted endpoint, and GRAPHIFY\_MCP\_TOKEN, a sensitive token for that project.

- Redeploy so a running deployment can see the variables.

The integration writes the credentials, but the app has to send them. In server-side code, send the token as an Authorization: Bearer header and read the URL from the environment. The token should stay out of browser code. The Vercel integration docs include sample calls for the AI SDK and for eve. The model id in that sample belongs to the listing, and Graphify does not choose the model.

## A token for each person

The Marketplace token is one token for the project. Vercel Connect is for apps where each person should authorize their own Graphify account, giving one token per person. From the project directory, the steps are vercel link, then vercel connect create graphify --name acme-graphify (the name is an example), then vercel env pull. The token id is graphify/ plus the chosen name. @vercel/connect getToken takes that id and the person's id, and the token it returns goes to https://api.graphify.com/mcp as a Bearer token. Both paths call the same hosted server as Graphify MCP.

If a coding agent is writing the app, the Connect page starts with Vercel's skill, npx skills add vercel/vercel-plugin --skill vercel-connect. That skill is Vercel's and is separate from graphify install.

## Requirements, revocation and troubleshooting

The repository must be indexed first, with agent access on. It can be added by signing in at app.graphify.com. Plan, limits and billing stay on Graphify pricing.

Disconnecting a project revokes that project's token. Removing the integration revokes every token from that installation. The Graphify account and subscription remain.

- Variables missing: the project was not selected, or it has not been redeployed.

- Token rejected: the project was disconnected, or the Bearer header is missing.

- getToken fails locally: run vercel env pull again.

- Empty answer: the repository is not indexed, or it is in another workspace.

![Graphify](<https://graphify.com/icon.png>)

Graphify

Turn a codebase into a knowledge graph your AI assistant can trace — answers come back as graph paths with real file:line citations.

[View Graphify →](<https://creatorstoolbox.com/resources/graphify>)

Sources

[Original source](<https://graphify.com/blog/vercel-integration>)

[Read Vercel integration on Creators Toolbox](<https://creatorstoolbox.com/blog/graphify-vercel-integration>)

---
Canonical source: https://creatorstoolbox.com/blog/graphify-vercel-integration