Skip to main content
Connect your Eve 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 in the Inkbox 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:
agent/connections/inkbox.ts
  1. 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 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. 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:
agent/connections/inkbox.ts
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 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 and Inkbox background tasks.