# Cross-link map: eve with Vercel Connect (/docs/connect/frameworks/eve)

> From the Vercel docs graph (built 2026-10-29T06:02:06.399Z), spanning vercel.com docs + KB, nextjs.org, ai-sdk.dev, and other Vercel documentation sites. Full graph as JSON: https://vercel.com/docs/graph.json

## Semantically closest pages

- [Vercel Connect](https://vercel.com/docs/connect) — Give your agents and services secure, short-lived access to third-party APIs like Slack, GitHub, Microsoft, and Snowflak
- [eve with MCP](https://vercel.com/docs/mcp/integrations/eve) — Give eve agents access to MCP tools through filesystem connections and authorize requests with Vercel Connect.
- [Authentication in Vercel Connect](https://vercel.com/docs/connect/concepts/authentication) — Every Vercel Connect token request has two legs that both have to authenticate: the caller calling Vercel Connect, and V
- [Chat SDK with Vercel Connect](https://vercel.com/docs/connect/frameworks/chat-sdk) — Use Vercel Connect credentials and trigger forwarding with Chat SDK adapters for Slack, Discord, Microsoft Teams, GitHub
- [Authenticating eve requests](https://vercel.com/docs/eve/authentication) — Configure access to eve HTTP routes, authenticate browser users, and provide user identities for Vercel Connect.

## This page links to (10)

- [vercel connect](https://vercel.com/docs/cli/connect) — Learn how to manage Vercel Connect connectors using the vercel connect CLI command.
- [Authentication in Vercel Connect](https://vercel.com/docs/connect/concepts/authentication) — Every Vercel Connect token request has two legs that both have to authenticate: the caller calling Vercel Connect, and V
- [Connectors in Vercel Connect](https://vercel.com/docs/connect/concepts/connectors) — A connector is the team-owned record that represents one third-party service. Its type determines which capabilities are
- [Connector installations in Vercel Connect](https://vercel.com/docs/connect/concepts/installations) — Installations let one connector serve many tenants. One Slack connector, for example, can serve many Slack workspaces, e
- [Project links in Vercel Connect](https://vercel.com/docs/connect/concepts/project-links) — A project link binds a connector to a Vercel project, scoped to one or more environments. The link is what authorizes a
- [Provider tokens in Vercel Connect](https://vercel.com/docs/connect/concepts/tokens) — Short-lived provider credentials issued by Vercel Connect. Each token request specifies a subject, optional installation
- [Webhook triggers for Vercel Connect](https://vercel.com/docs/connect/concepts/triggers) — Incoming webhooks from third-party services, verified by Vercel Connect and forwarded to your projects.
- [Quickstart](https://vercel.com/docs/connect/quickstart) — Create your first connector in Vercel Connect, install the SDK, and request a runtime provider token from your code.
- [TypeScript SDK Reference](https://vercel.com/docs/connect/ts-sdk-reference) — API reference for @vercel/connect, the TypeScript SDK for requesting runtime tokens from Vercel Connect.
- [Authenticating eve requests](https://vercel.com/docs/eve/authentication) — Configure access to eve HTTP routes, authenticate browser users, and provide user identities for Vercel Connect.

## Pages that link here (8)

By site: vercel-changelog (1) · vercel-docs (7)

### From vercel-changelog

- [Vercel Connect now supports Microsoft Teams](https://vercel.com/changelog/vercel-connect-microsoft-teams)

### From vercel-docs

- [Frameworks and Adapters for Vercel Connect](https://vercel.com/docs/connect/frameworks) — Use Vercel Connect with AI SDK, TanStack AI, MCP clients, eve, Chat SDK, Better Auth, and Auth.js.
- [eve](https://vercel.com/docs/eve) — Build and deploy durable backend AI agents with eve, an open-source, filesystem-first framework.
- [Authenticating eve requests](https://vercel.com/docs/eve/authentication) — Configure access to eve HTTP routes, authenticate browser users, and provide user identities for Vercel Connect.
- [Deploying eve to Vercel](https://vercel.com/docs/eve/deploying) — Link an eve project, configure production access, deploy the agent, and verify its runs on Vercel.
- [Getting started with eve](https://vercel.com/docs/eve/getting-started) — Create an eve agent, connect a model, and send your first message from the terminal.
- [MCP Integrations](https://vercel.com/docs/mcp/integrations) — Connect AI SDK, TanStack AI, and eve applications to MCP servers to discover and call tools.
- [eve with MCP](https://vercel.com/docs/mcp/integrations/eve) — Give eve agents access to MCP tools through filesystem connections and authorize requests with Vercel Connect.