mcpbeat Sign in

Bilg MCP Server

answering

Bilg is answering right now. Last checked 7 min ago.

Shared memory for coding agents and their teams: docs, epics, tasks and decisions over MCP.

Uptime history 19 hours of history
19 hours agonow
100.0%
Uptime 24h
70 of 70 checks
Tools
hidden behind auth
200 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Bilg 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 7 min ago.

run in your terminal
claude mcp add bilg --transport http https://mcp.bilgai.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "bilg": {
      "url": "https://mcp.bilgai.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.bilg]
url = "https://mcp.bilgai.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "bilg": {
      "url": "https://mcp.bilgai.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "bilg": {
      "url": "https://mcp.bilgai.com/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://mcp.bilgai.com/mcp streamable-http sign-in 212 ms 7 min ago

Alternatives to Bilg

same job, measured the same way
Robells
by robells

The shared task board for teams and their AI agents — connect over OAuth, every action signed.

answering
C
FrameOn
by frameonlab

Shared project memory for teams: read projects and tasks, write updates and wiki decisions.

answering
TeamShared
by xhad

Shared memory for coding agents. Stop re-explaining your codebase every session.

92 tools answering
OneLore
by onelore

Shared project context for AI agents and teams: docs, tasks, and messages that stay current.

answering
memsprout
by memsprout

shared AI-context layer for teams — persistent memory your agents search and update over MCP

answering
UNBLOCK
by kaeva-labs

UNBLOCK org-brain — shared memory and comms for human + agent teams. By Kaeva Labs.

answering
Runlane
by runlane

Kanban board for teams and coding agents: manage tasks, subtasks, sprints and wiki pages via MCP.

answering
Taskfolk
by taskfolk

Project management for teams and their AI agents.

answering

Bilg — questions

Answers built from our own checks of this server.

Why is there no tool list for Bilg?
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 Bilg working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 70 of 70 checks got a reply (100.0%), average response time 200 ms. The bar chart above shows every period we have measured.
How do I connect Bilg?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 Bilg?
No API key is involved. Bilg 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 Bilg?
It answers our handshake in 200 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.