Knowledge Base

ai.b77Published by b77.aiOfficial publisherv1.0.0Updated Oct 24, 2026

A searchable knowledge base your assistant reads and writes.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote, OAuth-protected knowledge base that an assistant can search, read from and write to.

What you can do
  • Search the knowledge base for stored entries.
  • Read entries and retrieve their content.
  • Add or update entries so the assistant can record information for later recall.
When to use it
When you want an assistant to keep a persistent, searchable store of notes or reference material across sessions, and to look things up in it rather than relying on conversation context alone.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so the user must sign in and authorize access. No environment variables or headers are declared.
Before you install
The assistant can write to the knowledge base, so entries may be added or changed without a separate confirmation step. Content stored there is held by the third-party provider rather than locally, and access is tied to the OAuth account you authorize.

Installation

In SourceWeft

  1. Open Knowledge Base 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/ai.b77%2Fknowledge-base/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": {
    "knowledge-base": {
      "type": "http",
      "url": "https://knowledge-base.b77.ai/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 16, 2026

Score

67% 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
  • 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.