# Vercel MCP, Next.js MCP and the errors your users see

You've connected Vercel MCP to your agent, a user says checkout is broken, and the agent finds nothing. That's usually because the error happened in the user's browser, and as Vercel documents it, the observability tools on Vercel MCP read Functions and daemon logs, not that browser session.

This guide is for Next.js teams on Vercel who already use an MCP-connected agent (Cursor, Claude Code or Codex). It shows what each MCP server reads, and one setup that adds real users' browser errors alongside them.

No account: `npx -y bugtape --help` prints the commands and does not sign you in. The demo MCP at https://app.bugtape.ai/demo/mcp needs no sign-in. Your own workspace needs one.

Page owner: Jaco Veldsman, hi@bugtape.ai. Last checked 2026-11-13. I build BugTape. Vercel and Next.js facts come from their public docs, linked below, re-checked on 13 November 2026.

## What each MCP server reads

| | Next.js MCP (`next-devtools-mcp`) | Vercel MCP | BugTape MCP |
|---|---|---|---|
| Where it runs | Your local `next dev` server (Next.js 16+, at `/_next/mcp`) | Your Vercel projects | Your BugTape project |
| Errors it returns | `get_errors`: config, build and browser runtime errors from browser sessions open on your dev server | `get_runtime_errors`: grouped runtime error clusters. `get_runtime_logs`: logs from Vercel Functions during requests (source: function or daemon), with a maximum lookback of 7 days | `list_recommended_critical`, `get_repro_context`: errors and bug reports captured in real users' browsers (and servers, if you add the Node SDK) |
| Production users' browsers | No, it reads your local dev session | Not as Vercel documents it: the logs come from Functions and daemon | Yes, once the browser SDK is installed |

Sources: [Next.js MCP guide](https://nextjs.org/docs/app/guides/mcp), [Vercel MCP observability tools](https://vercel.com/docs/agent-resources/vercel-mcp/tools/observability), [BugTape MCP tools](/docs/mcp-tools/).

They don't overlap much. Keep all three connected: the Next.js MCP while you build, Vercel MCP for function failures and logs, and BugTape for what broke in a real user's tab.

If you already run Grafana Faro, [Grafana Cloud MCP](https://grafana.com/docs/grafana-cloud/platform/grafana-assistant/configure/cloud-mcp/) does expose real-user browser errors when Faro is installed (`frontend_observability_handler`). BugTape adds the repro context for one user's steps. See [BugTape and Grafana Faro](/compare/grafana-faro/).

## Add browser capture to your Next.js app

Create `app/bugtape-provider.tsx` and render `<BugTapeProvider />` once from `app/layout.tsx`, after your consent check. Use the project capture key from BugTape Setup.

```tsx
import Script from 'next/script';

export function BugTapeProvider() {
  return (
    <Script id="bugtape" type="module" strategy="afterInteractive">
      {`
        import { init } from 'https://app.bugtape.ai/bugtape.mjs';
        init({
          apiKey: 'YOUR_PROJECT_KEY',
          onSuccess(response) {
            console.info('BugTape capture accepted', response.id, response.captureId);
          },
          onError(error) {
            console.warn('BugTape capture failed', error.message);
          }
        });
      `}
    </Script>
  );
}
```

This is the supported recipe from BugTape's [Next.js example](https://github.com/jackfieldman/bugtape/blob/main/docs/examples/nextjs/README.md). Prefer a bundled SDK? `npm install @bugtape/sdk` and call `BugTape.init({ apiKey })` once in a client component.

Two rules from that recipe and the [quickstart](/docs/quickstart/): render one provider only, and don't run it next to a second global error reporter. A capture key can only send events. Never put agent tokens or AI provider keys in the script.

In the browser, BugTape records uncaught errors, unhandled rejections, console breadcrumbs, the fetch and XHR waterfall, and a DOM replay ([what each platform captures](/docs/platforms/)).

**Server errors too?** Add `@bugtape/node` and the Next.js `onRequestError` hook ([cookbook](/blog/node-express-nextjs-bugtape/)). Then a function failure Vercel MCP shows you and the browser error that came with it end up in the same BugTape project.

## Check it

In a local or staging page, add a button that throws an error with a unique name. Click it, then open **Issues** in the BugTape console and find it. BugTape's own docs say this Next.js recipe has been checked for syntax and against the framework docs, and that a full Next.js runtime trial is still a separate check, so run this step yourself before you rely on it.

## Connect it to your agent

Do this after the capture key is in the app and a test error has landed.

```bash
npx -y bugtape connect cursor
```

Use `claude` or `codex` instead of `cursor` for the other clients ([install guide](/blog/install-bugtape-mcp-claude-cursor-codex/)).

Then, when a user reports a bug, ask your agent something like: *"Check Vercel runtime errors for /api/checkout in the last 24h, then pull the BugTape repro context for the checkout bug."* The agent calls Vercel's `get_runtime_errors` for the function side and BugTape's `get_repro_context` for the browser side: the error, the console and network timeline, and the steps before it. It can then open a pull request for you to review. BugTape doesn't change your code, merge or deploy.

## Why it pays off

The bugs users report are often front-end bugs: a failed fetch, a render that throws, a button that does nothing. When your agent can read the user's browser session next to the function logs, it can start on a fix without you first reproducing the bug by hand.

## FAQ

### Does BugTape replace Vercel MCP?

No. Vercel MCP covers your deployments, function logs and traces. BugTape adds browser-side capture and bug reports. Use both.

### Isn't the Next.js MCP enough?

It's very good while you develop, but it reads the browser sessions open on your own dev server, not your production users.

### Can Vercel MCP see production browser errors?

Not as Vercel documents it. `get_runtime_logs` reads output from Vercel Functions during requests (source: function or daemon). `get_runtime_errors` groups those runtime error clusters. This page does not claim those tools can never see a browser error; it follows the current docs.

### Is this a Vercel integration?

No. BugTape is a separate service you add to your app. It works the same whether or not you host on Vercel.

### Does this swap in for a Sentry DSN?

No. BugTape has its own SDK and `init`. To compare them, see [BugTape vs Sentry](/compare/sentry/).

## Sources

Re-checked 13 November 2026:

- [Vercel MCP observability tools](https://vercel.com/docs/agent-resources/vercel-mcp/tools/observability) (`get_runtime_errors`, `get_runtime_logs`, 7-day max lookback, source = function or daemon)
- [Next.js MCP guide](https://nextjs.org/docs/app/guides/mcp) (`next-devtools-mcp`, `/_next/mcp`, `get_errors` reads the current error state including browser runtime errors from dev-server sessions)
- [Next.js PR #84161](https://github.com/vercel/next.js/pull/84161)
- [Grafana Cloud MCP tools](https://grafana.com/docs/grafana-cloud/platform/grafana-assistant/configure/cloud-mcp/) (`frontend_observability_handler`)
- BugTape [quickstart](/docs/quickstart/), [Next.js example](https://github.com/jackfieldman/bugtape/blob/main/docs/examples/nextjs/README.md), [platforms](/docs/platforms/) and [MCP tools](/docs/mcp-tools/)

## See also

[Vercel FUNCTION_INVOCATION_FAILED](/guides/vercel-function-invocation-failed/) · [Node.js, Express and Next.js cookbook](/blog/node-express-nextjs-bugtape/) · [BugTape and Grafana Faro](/compare/grafana-faro/) · [Connect Cursor](/connect/cursor/) · [Install BugTape MCP](/blog/install-bugtape-mcp-claude-cursor-codex/) · [MCP tools](/docs/mcp-tools/) · [BugTape vs Sentry](/compare/sentry/)

[Start free](/console/register?utm_source=bugtape_seo&utm_campaign=vercel-mcp-production-browser-errors). No card.

Your team reviews the PR. Agents do not silent-ship.
