ci: Update MCP login to use inline private key

[masnwilliams]

TL;DR

Updated the CI workflow to use an inline private key for MCP authentication instead of a file.

Why we made these changes

Using an inline private key from a GitHub secret simplifies the authentication process in our CI workflow. It removes the need to manage a key file on the runner, which can be prone to permission issues and adds unnecessary complexity.

What changed?

• Modified .github/workflows/publish-mcp.yml to pass the private key for MCP login directly from a GitHub secret, removing the step that created a key file.

^{Description generated by Mesa. Update settings}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
mcp	Ready	Preview	Comment	Sep 10, 2025 9:57pm

[mesa-dot-dev]

Performed full review of 75f2975...88bdad3

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

• Configure your agents

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{1 files reviewed | 1 comments | Review on Mesa | Edit Reviewer Settings}

[mesa-dot-dev]

This openssl command chain is fragile and may break with different key formats or openssl versions. The grep pattern 'priv:' and text processing with tail/tr assumes a specific output format that isn't guaranteed. Consider using a more robust approach like openssl pkey -in key.pem -traditional to output the key in a standard format, or stick with the file-based approach which is more reliable and standard practice for CI/CD workflows.
_{Agent: 🤖 General}