Context Engine

io.github.relote-comPublished by GitHub account relote-comv1.0.0Updated Nov 7, 2026

One memory for your AI agents and your team: Claude, ChatGPT, Cursor and your agents share it.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Context Engine is a hosted memory service that lets AI assistants and agents share one memory with each other and with a team.

What you can do
  • Provides a shared memory that assistants such as Claude, ChatGPT and Cursor, plus custom agents, can draw on.
  • No tool list, instructions or documentation were supplied, so the specific actions an assistant can take are not described here.
  • Access is through a remote hosted endpoint rather than a local package.
When to use it
Consider it when you want several assistants or agents, and possibly teammates, to work from the same stored context instead of repeating background in each session.
Requirements
A remote endpoint at app.contextengine.com over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
Memory is shared across assistants and a team, so anything stored may be visible to others with access; review what gets written before relying on it. Sign-in is via OAuth to a third-party hosted service.

Installation

In SourceWeft

  1. Open Context Engine 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/io.github.relote-com%2Fcontext-engine/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": {
    "context-engine": {
      "type": "http",
      "url": "https://app.contextengine.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.0LatestNov 7, 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.