Skip to content

Latest commit

 

History

History
118 lines (91 loc) · 2.52 KB

File metadata and controls

118 lines (91 loc) · 2.52 KB

Release Guide for Flutter MCP Server

✅ Package Status

The package has been successfully built and is ready for publication:

  • PyPI Package: flutter_mcp_server-0.1.0
  • npm Package: @flutter-mcp/server@0.1.0

🚀 Publishing to PyPI

1. Create PyPI Account

2. Get API Token

3. Publish to TestPyPI (Recommended First)

# Set your TestPyPI token
export TWINE_USERNAME=__token__
export TWINE_PASSWORD=<your-test-pypi-token>

# Upload to TestPyPI
twine upload --repository testpypi dist/*

# Test installation
pip install -i https://test.pypi.org/simple/ flutter-mcp-server

4. Publish to PyPI

# Set your PyPI token
export TWINE_USERNAME=__token__
export TWINE_PASSWORD=<your-pypi-token>

# Upload to PyPI
twine upload dist/*

5. Verify Installation

pip install flutter-mcp-server
flutter-mcp --version

📦 Publishing npm Package

1. Login to npm

npm login

2. Publish the Package

cd npm-wrapper
./publish.sh

3. Verify Installation

npx @flutter-mcp/server --version

🎉 What's New in This Release

Transport Support (v0.1.0)

  • STDIO Transport (default) - For Claude Desktop and most MCP clients
  • HTTP Transport - For MCP SuperAssistant and HTTP-based clients
  • SSE Transport - For Server-Sent Events based clients

Usage Examples

HTTP Transport (for MCP SuperAssistant)

flutter-mcp start --transport http --port 8000

SSE Transport

flutter-mcp start --transport sse --port 8080

Custom Host Binding

flutter-mcp start --transport http --host 0.0.0.0 --port 3000

📝 Post-Release Checklist

  • Upload to TestPyPI and test
  • Upload to PyPI
  • Publish npm package
  • Create GitHub release with tag v0.1.0
  • Update the main README if needed
  • Announce in relevant communities

🔧 Troubleshooting

"Package already exists"

The package name might be taken. Check:

Build Issues

# Clean and rebuild
rm -rf dist/ build/ *.egg-info src/*.egg-info
python -m build

npm Login Issues

npm whoami  # Check if logged in
npm login   # Login again if needed