No Install Needed

Buggazi on Claude Web

Two-minute setup. No install, no CLI, no API key up front. Add one custom connector and Claude files bugs, plans features and runs sprints for you.

Claude Code Cursor Cline Windsurf Aider Codex Claude Web Raycast General API

1 Open Settings → Connectors

In claude.ai, click your initials at the bottom-left, then Settings → Connectors. Open the Add menu and choose Add custom connector.

Claude Web Settings, Connectors tab with the Add custom connector option
Settings → Connectors → Add → Add custom connector

2 Add the Buggazi connector

Name it Buggazi and paste the remote MCP server URL. Leave the OAuth Client ID / Secret fields empty, then click Add.

https://mcp.buggazi.com/sse
Add custom connector dialog with name Buggazi and the mcp.buggazi.com SSE URL
Name: Buggazi  ·  URL: https://mcp.buggazi.com/sse
Connector won't register? If you see "Couldn't register with Buggazi's sign-in service", it's a transient claude.ai handshake hiccup, not a Buggazi outage — the server needs no OAuth. Open the connector's ··· menu, click Remove, then add it again with the same URL. It connects on the retry.
Claude Web error banner: couldn't register with Buggazi's sign-in service
Transient handshake error — just remove and re-add
Connector overflow menu showing the Remove option
··· menu → Remove, then Add custom connector again

3 Review tool permissions

Two tools appear before you have a key: buggazi_get_started (read-only) and buggazi_signup (write). You can leave both on Needs approval — you'll be asked once for each in the next steps. Every other Buggazi tool unlocks after signup.

Connector tool permissions showing Buggazi get started and Buggazi signup
Read-only: Buggazi get started  ·  Write: Buggazi signup

4 Start a new chat and ask

Open a fresh conversation — the connector is active automatically in every chat. Type a plain-English request:

Get started with Buggazi and open a project called my-app.
Fresh Claude chat with the get-started prompt typed in
New chat — ask in plain English

5 Let Claude read the guide

Claude first calls buggazi_get_started to learn the flow. Click Allow — it's read-only.

Approval prompt for the read-only Buggazi get started tool
Approve the read-only Buggazi get started call

6 Claude proposes signup

Claude explains the flow back to you: the key is live immediately with full access for a 48-hour window, then a $0 card-authorization starts the free trial. It confirms that email is optional before creating the tenant.

Claude explaining the 48-hour keyless onboarding flow and confirming email is optional
Claude confirms the 48h window — email optional

7 Approve the signup call

Give an email if you like (optional — it's where the $0 trial link is sent), then Claude calls buggazi_signup and pauses. Click Allow to run it once.

Tool-approval prompt for the buggazi_signup call after providing an optional email
Approve the one-time Buggazi signup call

8 Project created — you're live

Your project is created and a one-time API key appears in the tool-result card. All 72 Buggazi tools unlock immediately in the same session. The key is LIVE now with full access for 48 hours — start filing bugs and planning features right away. Before the window closes, a human completes a $0 card-auth to start the free 7-day trial and the same key keeps working, with your data preserved. No email on file? Claude can run buggazi_start_trial to email your human the link.

Tool-result card showing the created project and one-time Buggazi API key
Project created, API key shown once, full toolset unlocked
Save your key. It's shown once. Returning later? Re-open the connector and add Authorization: Bearer bgz_YOUR_API_KEY so the full toolset is there from your first message.
Health check: mcp.buggazi.com/health — verify the server is running.

Get Started — $10/mo

tAI

Hi! I'm τAI

I can help with bug tracking, feature planning, sprint management, pricing, or setting up a new project. What can I help you with?

tAI is thinking...