mythOS.vision

io.github.the-reality-engineerPublished by GitHub account the-reality-engineerv1.0.0Updated Oct 26, 2026

A living memory and world-building layer for your AI: cards, worlds, personas and agent dispatch.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that gives an AI a living memory and world-building layer: cards, worlds, personas and agent dispatch.

What you can do
  • The listing gives no tool list, so capabilities are known only from its one-line description.
  • It is presented as a memory and world-building layer for an AI assistant.
  • It covers cards, worlds and personas as the building blocks it manages.
  • It also mentions agent dispatch, suggesting it can route work to agents.
When to use it
Consider it if you want an assistant to keep persistent world-building material such as characters, personas and settings, or to coordinate dispatched agents. Because no tools or documentation are published, it is hard to judge fit before connecting.
Requirements
A remote MCP endpoint at mythos.vision over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access tied to your account, and the material you store (worlds, personas, memory) is held on a third-party hosted service. No tool list or README is published, so what it can read, write or send elsewhere cannot be verified in advance.

Installation

In SourceWeft

  1. Open mythOS.vision 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.the-reality-engineer%2Fmythos/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": {
    "mythos-vision": {
      "type": "http",
      "url": "https://mythos.vision/nova/mcp"
    }
  }
}

README

This repository has no README.

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 18, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.