SilvaLabs

io.github.opensylvaPublished by GitHub account opensylvav1.0.0Updated Nov 19, 2026

Personal knowledge base MCP: agents read only materials you open.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that gives an assistant read access to a personal knowledge base, limited to materials you open.

What you can do
  • Connect an assistant to a personal knowledge base over a remote endpoint.
  • Let the assistant read materials from that knowledge base, restricted to items you have opened.
  • No individual tools are documented, so the exact read and search operations are not described in the listing.
When to use it
Useful if you keep reference material in a personal knowledge base and want an assistant to consult it while you work, with access limited to what you have opened.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. A bearer API key is required in the Authorization header, created through the provider's hub.
Before you install
You must supply a bearer API key in the Authorization header; keep it private and revoke it if exposed. Access is described as limited to materials you open, but the listing gives no detail on what is stored or sent to the provider, so review that before connecting sensitive material.

Installation

In SourceWeft

  1. Open SilvaLabs in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.opensylva%2Fsilvalabs/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.

{
  "mcpServers": {
    "silvalabs": {
      "type": "http",
      "url": "https://mcp.silvalabs.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 19, 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.