mcpbeat Sign in

Bilg MCP Server

answering

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

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

Uptime history 46 days of history · worst day 93%
46 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
234 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 3 min ago.

run in your terminal
claude mcp add bilg --transport http https://mcp.bilgai.com/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "bilg": {
      "type": "http",
      "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 180 ms 3 min ago

Alternatives to Bilg

same job, measured the same way
Evc Mesh MCP
by entire-vc

Tasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.

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
Hilbana
by hilbana

Project tracker for teams working with AI agents: issues, cycles, docs and shared agent memory.

answering
iKanban
by i-kanban

Tasks, sprints, releases and docs for engineering teams with AI coding agents.

answering
Vinktar
by vinktar

Error tracking for small teams and their coding agents.

31 tools answering
Korpus
by korpus

Shared memory for teams and their AI agents: Markdown concepts with typed links in shared bundles.

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 91 of 91 checks got a reply (100.0%), average response time 234 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 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 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 234 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.