# Neon + Vercel — Pipedream Connect

> Connect a user's Neon and Vercel accounts and expose tools for both apps directly in your product or your agent.

- Apps: Neon (`neon_api_keys`) + Vercel (`vercel_token_auth`)
- This page (HTML): https://pipedream.com/apps/neon-api-keys/integrations/vercel-token-auth
- One `external_user_id` owns both connected accounts, and each account stays independently revocable.

## One session, both toolsets (recommended)

- Endpoint: `https://remote.mcp.pipedream.net/v3`
- Headers: `Authorization: Bearer <token>` · `x-pd-project-id` · `x-pd-environment` · `x-pd-external-user-id` · `x-pd-app-slug: neon_api_keys,vercel_token_auth`
- `x-pd-app-slug` takes a comma-separated list, so `neon_api_keys,vercel_token_auth` is one session on one transport. Both toolsets arrive from a single `listTools()`, and a tool is called exactly as it would be in a single-app session.

```ts
import { Client } from "@modelcontextprotocol/sdk/client/index.js"
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const accessToken = await pd.rawAccessToken

const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": process.env.PIPEDREAM_PROJECT_ID!,
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "neon_api_keys,vercel_token_auth",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// One list, both toolsets: Neon and Vercel tools arrive
// together, each keyed by its own app's slug.

// e.g. run Create Branch:
const result = await mcp.callTool({
  name: "neon_api_keys-create-branch",
  arguments: {
    projectId: "Project ID",
    branchId: "Parent Branch ID",
  },
})
```

Docs: [MCP guide](https://pipedream.com/docs/connect/mcp/developers.md)

## Both apps from your backend

```ts
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const externalUserId = "{external_user_id}" // any stable ID for this user in your system

const [neonApiKeysTools, vercelTokenAuthTools] =
  await Promise.all([
    pd.components.list({ app: "neon_api_keys" }),
    pd.components.list({ app: "vercel_token_auth" }),
  ])

// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.
```

Docs: [Managed auth guide](https://pipedream.com/docs/connect/managed-auth/quickstart.md) · [Tools guide](https://pipedream.com/docs/connect/components.md)

## Neon

- API slug: `neon_api_keys` (use in MCP headers and tool keys)
- Auth: API key (Pipedream-managed)
- Categories: Data Analytics
- Website: https://neon.tech/
- App page (HTML): https://pipedream.com/apps/neon-api-keys
- Tools: 4 actions · 0 triggers

Full tool list, API proxy, and SDK quickstart: https://pipedream.com/apps/neon-api-keys.md

### Actions (4)

- [Create Branch](https://pipedream.com/apps/neon-api-keys/actions/create-branch.md) — `neon_api_keys-create-branch`
- [Create Database](https://pipedream.com/apps/neon-api-keys/actions/create-database.md) — `neon_api_keys-create-database`
- [Create Project](https://pipedream.com/apps/neon-api-keys/actions/create-project.md) — `neon_api_keys-create-project`
- [List Project ID Options](https://pipedream.com/apps/neon-api-keys/actions/list-project-id-options.md) — `neon_api_keys-list-project-id-options`

## Vercel

- API slug: `vercel_token_auth` (use in MCP headers and tool keys)
- Auth: API key (Pipedream-managed)
- Categories: Infrastructure & Cloud
- Website: https://vercel.com/
- App page (HTML): https://pipedream.com/apps/vercel-token-auth
- Tools: 3 actions · 5 triggers

Full tool list, API proxy, and SDK quickstart: https://pipedream.com/apps/vercel-token-auth.md

### Actions (3)

- [Cancel Deployment](https://pipedream.com/apps/vercel-token-auth/actions/cancel-deployment.md) — `vercel_token_auth-cancel-deployment`
- [Create Deployment](https://pipedream.com/apps/vercel-token-auth/actions/create-deployment.md) — `vercel_token_auth-create-deployment`
- [List Deployments](https://pipedream.com/apps/vercel-token-auth/actions/list-deployments.md) — `vercel_token_auth-list-deployments`

### Triggers (top 4 of 5)

- [Deployment Canceled (Instant)](https://pipedream.com/apps/vercel-token-auth/triggers/deployment-canceled-instant.md) — `vercel_token_auth-deployment-canceled-instant`
- [Deployment Error (Instant)](https://pipedream.com/apps/vercel-token-auth/triggers/deployment-error-instant.md) — `vercel_token_auth-deployment-error-instant`
- [Deployment Succeeded (Instant)](https://pipedream.com/apps/vercel-token-auth/triggers/deployment-succeeded-instant.md) — `vercel_token_auth-deployment-succeeded-instant`
- [New Deployment](https://pipedream.com/apps/vercel-token-auth/triggers/new-deployment.md) — `vercel_token_auth-new-deployment`

---

- Neon: https://pipedream.com/apps/neon-api-keys.md · Vercel: https://pipedream.com/apps/vercel-token-auth.md
- All apps: https://pipedream.com/apps — index: https://pipedream.com/llms.txt
- Pipedream docs for agents: https://pipedream.com/docs/llms.txt