v1.6.1 — WordPress.org compliance fixes

Removes blockers flagged by the WordPress.org automated submission check.

Removed (required by WP.org guidelines)

• GitHub auto-updater (includes/class-github-updater.php, the Update URI: header in the main plugin file, and the GithubUpdater::init() call in class-plugin.php). WP.org plugins must not ship their own update mechanism.

Fixed

• Heredoc syntax in includes/admin/views/partials/token-snippets.php. The Python and Node snippet templates are now built via plain string concatenation. PluginCheck.CodeAnalysis.Heredoc.NotAllowed no longer triggers.

What you lose

Until the plugin is approved on WordPress.org, there is no in-place update mechanism. Until then:

• Watch the GitHub releases page for new versions.
• Download and upload manually via Plugins → Add New → Upload Plugin → "Replace current with uploaded" (the folder name stays mcp-for-claude from 1.6.0 onward, so WP detects the existing install).

Once approved on .org, WP-core auto-updates resume automatically from the .org channel.