Repository navigation
MeiGen 4.0.0 replaces the local MCP implementation with a lightweight connection bridge to the hosted MeiGen service. Tool definitions, model options, instructions and results now come from the remote server, so ordinary server-side improvements no longer require an npm update.
Connect
Native remote MCP is recommended: https://www.meigen.ai/api/mcp, using your client's OAuth sign-in flow. No Node.js installation is needed for native remote connections.
For clients that require stdio:
{"mcpServers":{"meigen":{"command":"npx","args":["-y","meigen@4.0.0"]}}}The npm bridge requires Node.js 22.19+; Node.js 24 is recommended. Existing pinned installations need an explicit version update and restart/reconnect.
What changes
meigenandmeigen-mcpforward tools and results to the hosted service.- New connections use OAuth. Existing MeiGen API keys retain their account identity; private-library features require OAuth.
- Compatible MCP Apps hosts can display the shared home, inspiration, favorites and generation-result interfaces. UI support depends on the host; text-only clients retain tool results.
- Generation-progress views use model-specific estimated timing. Estimates are not provider-reported completion percentages.
Breaking changes and migration
Local BYOK, local file processing and automatic downloads, local preferences, local prompt enhancement, and the meigen gen CLI remain in 3.4.0. Keep that version if your workflow depends on them. Existing local connections are not silently converted, and an invalid fixed API key does not silently switch to OAuth.
Read the migration and rollback guide and setup guide. The v3.4.0 source and published npm package remain available.
Publication and verification
meigen@4.0.0 on npm is published. The public archive contains 35 files and matches the reviewed staged archive byte for byte. SHA-1: fa69aaac2cfc1842fa5887bcbfeafa85ebf02d21.
Linux and Windows CI passed. The downloaded npm artifact exposed 30 live tools and successfully queried the model catalog without a paid generation. The npm runtime was built from 3f40bdd; this release tag also includes subsequent test, CI and publication-documentation corrections, with no npm runtime changes. Immutable npm-bundled guides retain their pre-publication wording; these GitHub guides reflect the published state.
This is the planned final npm feature migration to remote delivery. Security, dependency or transport-compatibility fixes may still require future bridge releases. Third-party marketplace publications are separate.