Skip to content

Features

MCP server: production data inside your AI assistant

Buglapse runs a remote MCP server, so an AI coding assistant can read your projects directly. Ask what the most frequent error this week is and where in the code it comes from — without pasting stack traces into the chat.

Get startedRead the docs

All Buglapse features

claude — acme-web
buglapse · MCP

What's the most frequent error in production this week?

buglapse.list_issues(environment: "production", period: "7d", sort: "events")

found 5 unresolved issues

buglapse.get_issue(key: "WEB-42")

stack trace and 1,284 events loaded

The most frequent one is WEB-42 — TypeError — with 1,284 events from 312 users since release web@2.14.0.

It's thrown at src/checkout/useCart.ts:48: coupons.find() returns undefined for an unknown coupon code, and coupon.id is read without a check. Want me to add a guard and a test?

MCP server

Ask about production from the editor

  • Works where you code

    Claude Code, Cursor and any other client that supports remote HTTP MCP servers. One command or a few lines of config to connect.

  • Strictly read-only

    No tool can modify, resolve or delete anything. The assistant can look at production, but cannot change it.

  • The whole picture

    Issues, exceptions with stack traces, source maps, traces with every span, logs, end users, releases and uptime monitors.

  • Limited to what a repo needs

    Restrict a connection to one organization or a single project with a header, so an assistant in a repository sees only that project.

How it works

Connect an assistant

  1. 1

    Create a personal token

    Open Profile, then Tokens, and create a token with the MCP scope. The value is shown once, so copy it right away.

  2. 2

    Add the server to your client

    Point the client at the MCP endpoint and pass the token in the Authorization header.

  3. 3

    Ask a question

    Start by asking the assistant to list your projects, then ask about issues, slow traces or what is down right now.

terminal
claude mcp add --transport http buglapse https://app.buglapse.com/mcp \
  --header "Authorization: Bearer YOUR_PERSONAL_TOKEN"

In detail

Tools and security

What the assistant can read

The server exposes tools to list and open issues, raw exceptions with their stack traces and end users, uploaded source maps, traces with timings and metrics, logs, releases with the issues first seen in them, and uptime monitors with their incidents. List tools accept the same search syntax as the dashboard, so the assistant can filter by environment, release, status or user just as you would. The prompt Buglapse prepares when you take an issue from an investigation to your local coding agent points it at this server, so the agent can read the rest of the data itself.

The same access as you

Every request is made as the owner of the token and reaches the projects that person can see in the dashboard, nothing more. The token travels in a header rather than in the URL, so it does not end up in logs or shell history. It can be revoked at any moment and stops working immediately, and the list of tokens shows when each one was last used.

On each plan

Compare all plans
On each plan
Free Pro Team
MCP serverIncludedIncludedIncluded
API access with a personal tokenNot includedIncludedIncluded

FAQ

Common questions

Still have questions?

Drop us a line — we'll help with setup, plans or self-hosting.

Contact us

or email hello@buglapse.com

Which AI clients are supported?
Any MCP client that supports remote servers over the Streamable HTTP transport, including Claude Code and Cursor.
Can the assistant resolve or change issues?
No. The MCP server is read-only by design. To let an agent write a fix, use Autofix, which opens a draft pull request for review.
Is one token tied to one project?
No, a token reaches every project you are a member of, on plans that include the MCP server. Use the scope header to narrow a connection down.

See also

Related features

AI Autofix

An AI agent that finds the root cause in your repository and opens a draft pull request.

Learn more: AI Autofix

Error tracking

Every error grouped into one issue with a readable stack trace, breadcrumbs, the steps to the error and the affected users.

Learn more: Error tracking

Logs

Structured logs next to errors and traces, searchable by message, level and attribute.

Learn more: Logs

Ready to see what's happening in your app?

Create a project on the free plan and send your first event in a couple of minutes.

Create your projectRead the quickstart

Still have questions? Email hello@buglapse.com