Skip to main content
Graphify for Vercel connects Vercel projects to Graphify’s hosted MCP server. Your app or agent can query indexed repositories for definitions, callers, dependencies, change impact, and repository knowledge with source references.

Choose a Vercel path

Graphify supports two Vercel paths. They call the same hosted MCP server, but the token is issued differently. Both paths call the same hosted server used by Graphify MCP for VS Code, Graphify MCP for JetBrains, ChatGPT, Codex, and Dots, and Graphify MCP for OpenClaw.

Marketplace integration

Use the Marketplace integration when a Vercel project needs a project-scoped MCP token managed from Vercel. When you connect Graphify from the Vercel Marketplace:
  • You authorize an existing Graphify workspace.
  • You choose the Vercel projects and deployment environments that should receive Graphify MCP access.
  • Each selected project gets its own MCP token.
  • The integration adds GRAPHIFY_MCP_URL and a sensitive GRAPHIFY_MCP_TOKEN to each selected project.
  • Your Graphify plan, usage limits, and billing stay with Graphify.

Before you start

  • You are a Graphify workspace owner or admin.
  • You have a repository indexed in Graphify, with agent access enabled.
  • You can select the Vercel projects and deployment environments that should receive Graphify MCP credentials.
  • You will keep the credentials in server-side code. Do not expose GRAPHIFY_MCP_TOKEN to browser code.
See pricing for Graphify plans.

1. Install from Vercel Marketplace

  1. Open Graphify for Vercel.
  2. Select Connect Account.
  3. Authorize the existing Graphify workspace.
  4. Select the Vercel projects that should receive Graphify MCP access.
  5. Choose deployment environments. Production is selected by default; preview access is optional.
After install, redeploy the selected projects so the new variables are available at runtime. For local development, pull project environment variables with the Vercel workflow you already use.

2. Check the environment variables

The integration adds two variables to each chosen project: Server-side code sends GRAPHIFY_MCP_TOKEN to the Graphify MCP server as a Bearer token. Use the GRAPHIFY_MCP_URL value from the project environment instead of hard-coding the endpoint.

3. Call Graphify from eve

eve is Vercel’s agent project. Put the connection in agent/connections/graphify.ts:
eve keeps the credential out of the model. Its static-token auth sends the token as a Bearer token when it connects to the MCP server.

4. Call Graphify from the AI SDK

The AI SDK can load tools from Graphify’s MCP server and pass them to a model. This sample reads the Marketplace variables from server-side code:
The model id above is the Vercel listing’s sample. Graphify does not choose the model for your app.

5. Manage or remove the integration

Use Configure in Vercel to manage the Graphify connection.
  • Disconnecting a project revokes that project’s token.
  • Removing the integration revokes every token from that installation.
  • Your Graphify account and subscription stay intact after removal.
  • Repository indexing and agent access are managed in Graphify.

Vercel Connect connector

Use Vercel Connect when each person using the app should authorize their own Graphify account. Connect gives your app a token for that person. The app sends that token to Graphify. acme-graphify below is the example name from the Connect listing. Pick your own. The token id is graphify/ plus that name. When you create a Graphify connector:
  • Vercel records the connection under your linked project.
  • The person using your app completes Graphify authorization.
  • Your app calls getToken at runtime for the current subject.
  • Graphify receives a Bearer token for that person, not the Marketplace project token.

Before you start

  • A Vercel account and the Vercel CLI. Connect is available on all Vercel plans. See Vercel Connect.
  • A Vercel project. vercel link attaches this directory to it. The project can be empty. It exists so Vercel can issue a token to your code.
  • A Graphify account. If you don’t have one yet, you can create one for free while connecting. The Free plan needs no card. See Plans and pricing.
  • At least one repository with the status Indexed. Connect a repository and wait for that status. See Repositories and builds.
If a coding agent is writing this Vercel app, the Connect listing’s first command installs Vercel’s Connect skill:
That skill is Vercel’s. It is separate from graphify install.

1. Create the connector

Open Graphify on Vercel Connect and choose Create Connector, or run this from the project directory:
vercel env pull writes a local VERCEL_OIDC_TOKEN so getToken can run on your machine. On a Vercel deployment, Vercel supplies that token. If a later call cannot authenticate, run vercel env pull again. The local token is short-lived. Details are in the Connect quickstart. Complete the Graphify authorization Vercel shows. The listing requests access for the person using the app, under that person’s Graphify permissions.

2. Ask Connect for a token

@vercel/connect is the Connect SDK. Install it, then call getToken with the id of the person using your app. user_123 below is a placeholder.
Send token to https://api.graphify.com/mcp as Authorization: Bearer <token>. The eve and AI SDK sections below do that for you.

3. Call Graphify

Use one of the two stacks from the listing, or send the Bearer token from your own route.

eve

eve is Vercel’s agent project. You declare Graphify as a connection, and eve attaches the tools.
Add agent/connections/graphify.ts:

AI SDK

The AI SDK is Vercel’s library for calling a model from your code and handing it tools. This sample is the one on the listing, including the model id.

If something fails

  • 429 rate_limited. The hosted MCP allows 240 requests a minute per client IP for signed-in sessions. Wait, then retry. See Troubleshooting.

Graphify MCP for VS Code

Connect an editor to the same hosted server.

Vercel Connect

How Connect issues a token and how a project is allowed to ask for one.