Milyoo

io.github.jmcitrinPublished by GitHub account jmcitrinv1.0.0Updated Nov 1, 2026

A home for your agents: an owned book of record any AI agent can write to, with provenance and undo.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Milyoo is a hosted "book of record" for AI agents: a shared, owned record that agents can write to, with provenance and undo.

What you can do
  • Write records into an owned book of record that any AI agent can contribute to
  • Track provenance so entries can be traced back to their source
  • Undo changes made to the record
  • Connect from any MCP-capable assistant over a remote endpoint
  • Tool-level details are not published in the listing, so exact operations are unconfirmed.
When to use it
Consider it when you want several agents or assistants to contribute to one persistent, auditable record that you own, and you need to trace or reverse what was written.
Requirements
A remote MCP endpoint at app.milyoo.ai over streamable HTTP. OAuth authentication is required, so a Milyoo account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server writes to a persistent record, so agent-made changes should be reviewed; undo is advertised but its scope is not documented. Sign-in is via OAuth, granting the server access to your Milyoo account. Content written to the record is stored with the hosted service.

Installation

In SourceWeft

  1. Open Milyoo 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.jmcitrin%2Fmilyoo/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": {
    "milyoo": {
      "type": "http",
      "url": "https://app.milyoo.ai/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 1, 2026

Score

83% 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
  • 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.