Import mcp-to-cli from the rhema workspace

The crate maps MCP tool catalogs to clap commands and back, and has no
rhema dependencies — it was in-tree only because the workspace glob
reached it. Its own repository gives it its own release cadence and
its own crates.io token, scoped to this crate alone.

tests/fixtures/create_issue.json

@@ -0,0 +1,41 @@
+{
+  "properties": {
+    "body": {
+      "description": "Issue body content (optional)",
+      "type": "string"
+    },
+    "owner": {
+      "description": "Repository owner (username or organization)",
+      "type": "string",
+      "x-mcp-header": "owner"
+    },
+    "parent_issue_number": {
+      "description": "Issue number of the parent issue. The new issue is created and attached to this parent in the same operation.",
+      "minimum": 1,
+      "type": "number"
+    },
+    "parent_owner": {
+      "description": "Repository owner of the parent issue. Must be provided with parent_repo. Omit both to use owner and repo. Only used when parent_issue_number is provided.",
+      "type": "string"
+    },
+    "parent_repo": {
+      "description": "Repository name of the parent issue. Must be provided with parent_owner. Omit both to use owner and repo. Only used when parent_issue_number is provided.",
+      "type": "string"
+    },
+    "repo": {
+      "description": "Repository name",
+      "type": "string",
+      "x-mcp-header": "repo"
+    },
+    "title": {
+      "description": "Issue title",
+      "type": "string"
+    }
+  },
+  "required": [
+    "owner",
+    "repo",
+    "title"
+  ],
+  "type": "object"
+}