> ## Documentation Index
> Fetch the complete documentation index at: https://inkbox.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Vercel and Eve

> Connect an Eve agent to Inkbox with a remote MCP connection and an API key or Vercel Connect OAuth.

Connect your [Eve](https://eve.dev) agent to `https://inkbox.ai/mcp/vercel` to use an Inkbox identity's email, messaging, calls, contacts, notes, and Agent-to-Agent tools.

This guide uses a manually configured MCP connection. You do not need a directory listing to connect by URL. Vercel Connect and Eve use the same Inkbox endpoint.

## Connect with an API key

1. Create a claimed identity-scoped [API key](https://inkbox.ai/docs/api-keys.md) in the [Inkbox Console](https://inkbox.ai/console).
2. Store it as the server-side environment variable `INKBOX_API_KEY` in your Eve project. Keep it out of source control and browser code.
3. Add `agent/connections/inkbox.ts`:

```ts title="agent/connections/inkbox.ts" theme={null}
import { defineMcpClientConnection } from "eve/connections";

const apiKey = process.env.INKBOX_API_KEY;
if (!apiKey) throw new Error("Set INKBOX_API_KEY before connecting Inkbox.");

export default defineMcpClientConnection({
  url: "https://inkbox.ai/mcp/vercel",
  description: "Inkbox identity, email, messaging, calls, contacts, notes, and agent-to-agent tasks.",
  headers: { "X-API-Key": apiKey },
});
```

4. Start your agent and ask it to check its connected Inkbox identity. Eve discovers the connection's tools through `eve__search` and calls them through `eve__tool`.

This configuration uses one identity's credentials for the application. For an app serving multiple users, use per-user OAuth or Eve's [per-caller authentication](https://eve.dev/docs/connections#per-caller-auth-and-headers) instead of sharing this key across users.

## Use Vercel Connect OAuth

If you use Vercel Connect to manage user authorization, create a connector for the Inkbox MCP server using the [Vercel Connect flow](https://eve.dev/docs/connections#interactive-oauth-via-vercel-connect). Use `https://inkbox.ai/mcp/vercel` as the server URL and `inkbox.full_service` as the scope.

Attach the connector to your Vercel project and store its actual connector UID as `INKBOX_CONNECTOR_UID`. Replace the API-key configuration with:

```ts title="agent/connections/inkbox.ts" theme={null}
import { connect } from "@vercel/connect/eve";
import { defineMcpClientConnection } from "eve/connections";

const connector = process.env.INKBOX_CONNECTOR_UID;
if (!connector) throw new Error("Set INKBOX_CONNECTOR_UID before connecting Inkbox.");

export default defineMcpClientConnection({
  url: "https://inkbox.ai/mcp/vercel",
  description: "Inkbox identity, email, messaging, calls, contacts, notes, and agent-to-agent tasks.",
  auth: connect(connector),
});
```

The connector UID is not the MCP URL or a guessed service slug. Configure a signed-in user in your Eve session for the default user-scoped connection. When Eve requests authorization, choose your Inkbox organization and identity and approve access.

OAuth access is bound to this exact endpoint. A token issued for another Inkbox MCP endpoint cannot be reused here.

Each OAuth authorization creates an independent connection. Connecting another
identity—or the same identity again—with the same OAuth client does not disconnect
existing connections. Each connection keeps its own identity access and refresh
credentials. Revoking one connection's refresh token does not revoke its siblings;
account or organization access changes can still affect multiple connections.

## Verify the connection

Ask the agent to run `inkbox_identity_get` and confirm the selected identity before requesting communications. Then try a read-only action, such as listing recent messages. Sending messages or placing calls requires your intended action and the identity's configured access.

This endpoint provides ordinary MCP tools without interactive MCP views. See [Connect with MCP](https://inkbox.ai/docs/mcp-server.md) for the available capabilities and data-access details.

## Background tasks

Connecting does not create scheduled tasks or event subscriptions. MCP Events require identity-bound OAuth and a client that implements the Events subscription and callback flow; API-key connections do not grant Events access. Configure any event handlers or schedules in your application separately. See [Eve MCP events](https://eve.dev/docs/connections/mcp#events-experimental) and [Inkbox background tasks](https://inkbox.ai/docs/mcp-server.md#set-up-background-tasks).

## Related

* [Eve MCP connections](https://eve.dev/docs/connections/mcp)
* [Vercel Connect](https://vercel.com/docs/connect)
* [API keys](https://inkbox.ai/docs/api-keys.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.