Repository navigation
Releases
Releases · nodemode-dev/formMCP
formMCP 0.10.4
- Connecting Codex no longer breaks a config.toml that holds a multi-line string (
"""or''') with a line such as[mcp_servers.formmcp]inside it. That text used to read as FormMCP's own section, so Codex showed as connected, and Connect rewrote the lines inside the string, closing quotes included, after which Codex could not load the file. Text inside a multi-line string is now never read as a section. - A Codex config.toml that is not valid TOML is refused with the reason (for example "line 1: unclosed table, expected
]") and left unchanged; the status shows the same reason. Before, Connect added FormMCP's section to the broken file and reported connected. Every Codex change is now also checked before it is saved: the result must be valid TOML, hold FormMCP's entry as written (or none after Remove) and leave every other setting the same, or nothing is written. - Connect and Remove in Cursor change only FormMCP's entry in mcp.json. Before, the whole file was rewritten: keys sorted, two-space indents,
1.50saved as1.5and escapes such aséturned into characters. Now every other byte stays as it was (indents, key order, numbers, escapes, Windows line endings and a byte order mark), the new entry is indented like its neighbours, and removing it gives back the file as it was before Connect. - The status of a Cursor mcp.json that is not plain JSON now says why it cannot be connected: FormMCP edits only plain JSON and leaves a file with comments or trailing commas alone. Connect still refuses such a file and changes nothing.
- Removing FormMCP from a Cursor mcp.json that had no
mcpServersbefore Connect gives back that file byte for byte. Before, Remove left an empty"mcpServers": {}behind. AnmcpServersobject the person wrote themselves is kept, empty, when FormMCP's entry was its only one, unless its bytes are exactly what Connect would have added.
Built by formcompiler from nodemode-dev/formMCP ref compile_v0.10.4 at f7084245b54b. SHA256SUMS.txt lists every file.
formMCP 0.10.3
- Connecting Codex no longer breaks its config.toml. A
formmcpentry written another valid way (a comment after the header, spaces or quotes in it, a byte order mark, orformmcp = { ... }under[mcp_servers]) used to read as not connected, and Connect added a second[mcp_servers.formmcp]table that Codex could not load. FormMCP now finds its section in any of those forms, and one it cannot edit shows as taken and is left alone. - Another agent's server named
formmcpis now really left alone. An entry counts as FormMCP's only when its command is FormMCP (theformmcplauncher,formmcp-cli, or the installed app); before, a foreign entry whose text mentioned formmcp anywhere (an env subtable, a package name such asformmcp-server, or Claude Code's own "claude mcp remove formmcp" hint) still read as connected and was replaced. - On Windows, Claude Code installed with npm is found and can be connected. FormMCP picked the extensionless shim in the npm folder, which Windows cannot run, instead of
claude.cmd. - A Codex or Cursor config that cannot be read (for example a Cursor file saved in a Windows code page, or one without read permission) is no longer replaced by a file holding only FormMCP. Connect refuses it with the reason, and the client's status shows the reason too.
- Before and after hook commands keep Windows paths:
C:\Tools\check.exeused to lose its backslashes, so a before hook refused every call. A backslash now escapes only a quote or another backslash. - A Cursor mcp.json saved with a byte order mark is read: it used to show as not connected and Connect refused it. The refusal for an mcp.json that is not valid JSON now also says that comments are not supported.
- Reconnecting or removing Codex keeps comments and blank lines that sit above the next server's section.
- Codex and Cursor configs are written to a temporary file and renamed into place, so an interrupted write cannot leave them empty; a symlinked config stays a link. Backups made in the same second no longer overwrite each other, and Connect on a client that is already connected with the same entry writes nothing and makes no backup.
./formmcp mcp --client codexpasses--clienton, as the wiki describes, andformmcp.bat cliandformmcp.bat familypass more than nine arguments.- An imported profile that names an app by its display name or in another casing (
FormVis) now takes effect: it is stored under the app's id.
Built by formcompiler from nodemode-dev/formMCP ref compile_v0.10.3 at 33706d1de805. SHA256SUMS.txt lists every file.
formMCP 0.10.1
- Each app card keeps its content inside its edge. With an app installed, the Tools button and the state pill (Live, Public, Coming) no longer spill past the card; a long installed line now ends in an ellipsis and the badge line wraps on a narrow card.
Built by formcompiler from nodemode-dev/formMCP ref compile_v0.10.1 at 6c6f54140d59. SHA256SUMS.txt lists every file.
formMCP 0.10.0
- The three demos open inside the app. A Demos button at the top right of the window shows a panel with one card per demo (its screenshot, title and what it shows); on macOS the Help menu has an item for each. A demo opens in a window of its own, the same page as the browser demo, in its prepared state: the window and the Lab, connecting agents, or safety and activity. It is a sandboxed copy that has no access to FormMCP's commands, so it never changes your settings, your agents' files, the keychain or any app; close the window to leave it.
- The demo pages ship in the app's bundle from their committed builds, so nothing new is added and every file stays credited in the demo's
CREDITS.md. - Agents can open a demo with the new MCP tool
demo_open(window,connectorsafety) while FormMCP's window is open. - The app's commands are now declared, and only the splash and main windows may call them.
- The browser demos are rebuilt for the version they show.
Built by formcompiler from nodemode-dev/formMCP ref compile_v0.10.0 at d6df0b60f1d5. SHA256SUMS.txt lists every file.
formMCP 0.9.1
- Merges Greg's pull request, docs(readme): updates come through FormPortal. FormMCP has no in-app updater, so the README's Download section now says FormPortal keeps it up to date, with a link, and that a new version can also be downloaded from the links above.
- Releases it with the extension host from v0.9.0 below. The app and the demos are otherwise unchanged; the demos are rebuilt for the version they show.
Built by formcompiler from nodemode-dev/formMCP ref compile_v0.9.1 at d440619c0312. SHA256SUMS.txt lists every file.
formMCP 0.7.8
- README in the Form family template (Mackin's #6), merged with main. Nothing in the app changed.
Built by formcompiler from nodemode-dev/formMCP ref compile_v0.7.8 at 818146c41b74. SHA256SUMS.txt lists every file.