Add PyPI badges, fix license format, add release process

Author: crowecawcaw

README.md

@@ -1,5 +1,8 @@
 # click-mcp
 
+[![PyPI version](https://badge.fury.io/py/click-mcp.svg)](https://badge.fury.io/py/click-mcp)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
 A Python library that extends Click applications with Model Context Protocol (MCP) support, allowing AI agents to interact with CLI tools.
 
 ## Overview

RELEASE_PROCESS.md

@@ -0,0 +1,70 @@
+# Release Process for click-mcp
+
+This document outlines the steps to release a new version of click-mcp.
+
+## 1. Update Version Number
+
+1. Edit `pyproject.toml` and update the version number:
+
+```toml
+[project]
+name = "click-mcp"
+version = "X.Y.Z"  # Update this line
+```
+
+2. Commit the change:
+
+```bash
+git add pyproject.toml
+git commit -m "Bump version to X.Y.Z"
+```
+
+## 2. Create a GitHub Release
+
+1. Push your changes to GitHub:
+
+```bash
+git push origin main
+```
+
+2. Go to the GitHub repository: https://github.com/crowecawcaw/click-mcp
+
+3. Click on "Releases" in the right sidebar
+
+4. Click "Create a new release"
+
+5. Enter the following information:
+   - Tag version: `vX.Y.Z` (e.g., `v0.1.1`)
+   - Release title: `Version X.Y.Z`
+   - Description: Add release notes describing the changes in this version
+
+6. Click "Publish release"
+
+## 3. Automatic PyPI Publishing
+
+The GitHub Actions workflow will automatically:
+1. Build the package
+2. Upload it to PyPI
+3. Make it available for installation via `pip install click-mcp`
+
+## 4. Verify the Release
+
+After the GitHub Actions workflow completes:
+
+1. Check that the package is available on PyPI: https://pypi.org/project/click-mcp/
+
+2. Test installation in a clean environment:
+
+```bash
+pip install click-mcp==X.Y.Z
+```
+
+## Version Numbering Guidelines
+
+Follow semantic versioning (SemVer):
+
+- **MAJOR** version (X): Incompatible API changes
+- **MINOR** version (Y): Add functionality in a backward-compatible manner
+- **PATCH** version (Z): Backward-compatible bug fixes
+
+For pre-releases, use suffixes like `-alpha.1`, `-beta.1`, etc.

pyproject.toml

@@ -11,11 +11,10 @@ authors = [
     {name = "Stephen Crowe"}
 ]
 requires-python = ">=3.8"
-license = {text = "MIT"}
+license = "MIT"
 classifiers = [
     "Development Status :: 4 - Beta",
     "Intended Audience :: Developers",
-    "License :: OSI Approved :: MIT License",
     "Programming Language :: Python :: 3",
     "Programming Language :: Python :: 3.8",
     "Programming Language :: Python :: 3.9",