Bilg

com.bilgaiPublished by bilgai.comOfficial publisherv1.0.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Bilg is a remote MCP server that gives coding agents and their teams shared memory for docs, epics, tasks and decisions.

What you can do
  • Share project memory across coding agents and teammates: docs, epics, tasks and decisions.
  • Read and contribute to the same project context from an assistant session over MCP.
  • Connect via a hosted remote endpoint, with OAuth or an API key for authentication.
When to use it
Useful when several coding agents or team members need a common, persistent record of project documentation, epics, tasks and decisions instead of each session starting from scratch.
Requirements
A remote MCP endpoint at mcp.bilgai.com over streamable HTTP. Authentication is required: either OAuth (supported by Claude Desktop and claude.ai) or an API key sent in the Authorization header as a bearer token, created in the Bilg app settings. No local package or runtime is needed.
Before you install
The server holds shared team project data, so anything an assistant writes may be visible to teammates and other agents. An API key is a secret sent in the Authorization header; keep it private and revoke it if exposed. Tool-level behavior is not documented in the listing, so confirm what the assistant can change before granting access.

Installation

In SourceWeft

  1. Open Bilg in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bilgai%2Fbilg/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bilg": {
      "type": "http",
      "url": "https://mcp.bilgai.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 17, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.