Context OS

top.contextlmPublished by contextlm.topOfficial publisherv1.0.0Updated Oct 24, 2026

Workspace knowledge bases agents ingest, search, and query over MCP.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Context OS is a remote MCP endpoint that lets an assistant ingest, search and query workspace knowledge bases.

What you can do
Ingest material into workspace knowledge bases so it can be retrieved later. Search and query those knowledge bases over MCP. The server exposes no listed tools, so the exact operations are not documented; the description only states that agents ingest, search and query knowledge bases through it.
When to use it
Useful when an assistant should answer from a shared workspace knowledge base rather than general knowledge, and when you want that retrieval hosted remotely instead of running a local server.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP. A bearer token is required in the Authorization header: a workspace API key minted in the project's share center. Network access to the endpoint.
Before you install
The connection requires a workspace API key sent in the Authorization header; treat it as a secret and keep it out of logs and shared configuration. Ingesting material sends your content to the provider's hosted service, so check what data is appropriate to upload. The tool list is not published, so confirm what write or delete operations are available before connecting.

Installation

In SourceWeft

  1. Open Context OS 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/top.contextlm%2Fcontext-os/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": {
    "context-os": {
      "type": "http",
      "url": "https://app.contextlm.top/api/v1/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.0LatestOct 15, 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.