Mymir is now Piyaz

[FrkAk]

Mymir has a new name: Piyaz. Same product, same flows, same accounts and data. The rename runs all the way through, covering the app, the plugins, the /piyaz skill, the MCP tools, and the domain.

A few things changed that you need to act on:

• The app moved from app.mymir.dev to app.piyaz.ai. The old domain is retired and does not redirect, so existing setups have to be updated by hand.
• The MCP endpoint is now https://app.piyaz.ai/api/mcp.
• The MCP server key in your config changed from mymir to piyaz, the skill is now /piyaz, and the env override is PIYAZ_URL (was MYMIR_URL).
• The MCP tools were renamed mymir_* → piyaz_* (piyaz_project, piyaz_task, piyaz_query, piyaz_analyze, piyaz_context, piyaz_edge). This is a breaking change: restart your session or reconnect the server so the client rediscovers the tools.
• Your first connection to the new server will ask you to authorize again.

If you use the plugin, reinstalling the piyaz plugin from the marketplace applies the new defaults. The repo also moved to github.com/FrkAk/piyaz (old links redirect, but update your remotes).

A couple of changes landed alongside the rename, mostly relevant if you self-host:

• The Postgres auth schema was renamed neon_auth → piyaz_auth so it stops colliding with Neon's reserved neon_auth schema (Piyaz self-manages its auth tables). (chore: rename auth schema to piyaz_auth and bump postgres to 18 #142)
• Local and CI Postgres moved from 17 to 18 to match production. PG 18 is a major bump and its Docker image changed the data volume path, so the simplest path is a clean bun run db:setup. (chore: rename auth schema to piyaz_auth and bump postgres to 18 #142)

There are breaking changes here, especially the MCP URL and the tool-name rename. If your setup is affected or something stops resolving, reply here or reach out to me and I will help you through it.