Graphify MCP for Vercel

Vercel Connect lets a Vercel app or agent call Graphify’s hosted MCP server at https://api.graphify.com/mcp as the person using that app. Graphify is a third-party connector in that catalog. The person authorizes the Graphify account they already have. Vercel does not create the account, and the Graphify plan stays the one on app.graphify.com. This is the same hosted server as Graphify MCP for VS Code, Graphify MCP for JetBrains, Graphify for ChatGPT, and Graphify MCP for OpenClaw. Connect’s job is the login token. The app sends that token to Graphify. acme-graphify on this page is the example name from the listing. Pick your own. The token id is graphify/ plus that name.

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 repository indexed in your Graphify workspace. Sign in at app.graphify.com, connect a repository, and wait until its status is Indexed. See Repositories and builds.

If a coding agent is writing this Vercel app, the listing’s first command installs Vercel’s Connect skill:

npx skills add vercel/vercel-plugin --skill vercel-connect

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 link
vercel connect create graphify --name acme-graphify
vercel env pull

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.

npm install @vercel/connect

import { getToken } from '@vercel/connect'

const userId = 'user_123'

const token = await getToken('graphify/acme-graphify', {
  subject: { type: 'user', id: userId },
})

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.

npx eve@latest init my-agent
cd my-agent
npm install @vercel/connect
vercel link
vercel connect create graphify --name acme-graphify
vercel env pull

Add agent/connections/graphify.ts:

import { defineMcpClientConnection } from 'eve/connections'
import { connect } from '@vercel/connect/eve'

export default defineMcpClientConnection({
  url: 'https://api.graphify.com/mcp',
  description: 'Graphify tools and data',
  auth: connect('graphify/acme-graphify'),
})

npm run dev

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.

npm install ai @ai-sdk/mcp @vercel/connect
vercel link
vercel connect create graphify --name acme-graphify
vercel env pull

import { getToken } from '@vercel/connect'
import { createMCPClient } from '@ai-sdk/mcp'
import { generateText, isStepCount } from 'ai'

const userId = 'user_123'
const token = await getToken('graphify/acme-graphify', {
  subject: { type: 'user', id: userId },
})

const client = await createMCPClient({
  transport: {
    type: 'http',
    url: 'https://api.graphify.com/mcp',
    headers: { Authorization: `Bearer ${token}` },
  },
})

try {
  const { text } = await generateText({
    model: 'openai/gpt-5.4',
    tools: await client.tools(),
    stopWhen: isStepCount(10),
    prompt: 'Use Graphify to help with this request.',
  })
} finally {
  await client.close()
}

If something fails

What you see	What to do
`getToken` cannot authenticate	Run `vercel env pull` again from the linked project. The local OIDC token expires. A deployment on Vercel receives its own token.
The token id is rejected	The id is `graphify/` plus the `--name` you passed to `vercel connect create`. `graphify/acme-graphify` matches the example name only.
No repositories, or empty answers	That repository is not indexed yet, or it is in a different workspace. Check its status in Repositories and builds.
The tools are the ten local ones	This page uses the hosted server. The ten-tool list in the MCP tool reference is the graph on the machine.

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.

​Before you start

​1. Create the connector

​2. Ask Connect for a token

​3. Call Graphify

​eve

​AI SDK

​If something fails

​Related