mcpbeat Sign in

Birdie MCP Server

answering

Birdie is answering right now. Last checked 14 min ago.

Search Birdie screen recordings: transcripts, console logs, network requests, repro steps, frames.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
472 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Birdie every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add birdie --transport http https://app.birdie.so/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.birdie.so/mcp
~/.codex/config.toml
[mcp_servers.birdie]
url = "https://app.birdie.so/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "birdie": {
      "url": "https://app.birdie.so/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "birdie": {
      "type": "http",
      "url": "https://app.birdie.so/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.birdie.so/mcp streamable-http sign-in 437 ms 14 min ago

Alternatives to Birdie

same job, measured the same way
Tracebug
by prashantsinghmangat

AI agents read TraceBug bug reports (console, network, replay, repro timeline) from local disk.

518 installs/wk local only
C
Chromedebug
by dynamicupgrade

Record browser bugs - frames, clicks and console logs - and hand them to your AI over MCP.

145 installs/wk local only
Browserdebug
by cloudcorprecords

Debug web pages in Chrome: performance traces, network, console, snapshots, screenshots.

305 installs/wk local only
Cortex RMCP
by dinglebear

Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.

local only
Verify SCITT receipts from Forestrie transparency logs, offline
by forestrie

Verify a SCITT receipt under a trust root you hold — offline, no backend, no key, no network

524 installs/wk local only
LogsLoom
by efim23

Ingest and search LogsLoom logs from coding agents.

25 installs/wk 4 tools answering
Patchwell
by patchwell

Cited web research, transcription with word timestamps, and CSV/Excel cleaning with a change log.

5 tools answering
yt
by arasandev

YouTube transcripts, transcript search, and channel monitoring for agents.

local only

Birdie — questions

Answers built from our own checks of this server.

Why is there no tool list for Birdie?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Birdie working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 472 ms. The bar chart above shows every period we have measured.
How do I connect Birdie?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Birdie?
No API key is involved. Birdie answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Birdie?
It answers our handshake in 472 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.