Computer Legend

com.computerlegendPublished by computerlegend.comOfficial publisherv1.0.0Updated Oct 26, 2026

Food, sleep, to-dos, songs, files, finance: one Computer Legend account your AI uses. You own it.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFinance

Overview

AI-generated overview

Remote MCP endpoint that connects an assistant to a Computer Legend account covering food, sleep, to-dos, songs, files and finance.

What you can do
  • No tool list is published, so capabilities are known only from the provider's description.
  • The account is described as spanning food, sleep, to-dos, songs, files and finance.
  • An assistant connects to it over a remote streamable HTTP endpoint rather than a local package.
  • The provider states the account belongs to the user.
When to use it
Consider it if you already use Computer Legend and want an AI assistant to work with the personal data held in that account across several everyday areas. It is not a fit if you need a documented tool list before connecting.
Requirements
A Computer Legend account with OAuth sign-in; the server is a hosted remote endpoint, so no local runtime or package is needed. No environment variables or headers are declared.
Before you install
The account is described as holding personal records such as food, sleep, to-dos, files and finance, so an assistant connected to it may read or change sensitive data; the published material does not say which tools exist or whether they write. Review what access you grant during OAuth.

Installation

In SourceWeft

  1. Open Computer Legend 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.computerlegend%2Fcomputer-legend/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": {
    "computer-legend": {
      "type": "http",
      "url": "https://api.computerlegend.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.0LatestOct 21, 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.