@myna-sh/cli 0.12.2 → 0.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -64,6 +64,31 @@ myna changes diff chs_...
64
64
 
65
65
  Run `myna --help` or `myna <command> --help` for the complete command reference. Global flags include `--json`, `--organization`, `--project`, `--token`, and `--api-url`.
66
66
 
67
+ ## Set up coding agents
68
+
69
+ ```sh
70
+ myna mcp install # write Myna's MCP server into every detected client
71
+ myna mcp list # which clients are here, and which have Myna configured
72
+ myna skills install # install the change-set, schema, and publishing rules
73
+ ```
74
+
75
+ `myna mcp install` never writes a credential into a client's config file — those
76
+ usually live in the repository — storing it in `~/.config/myna/mcp.json` at
77
+ `0600`, where `@myna-sh/mcp` already looks. Use `--transport http` to point at
78
+ the hosted server over OAuth, where no stored credential is needed at all.
79
+
80
+ ## Call anything
81
+
82
+ ```sh
83
+ myna api /projects/my-site/entries?collection=posts
84
+ myna api POST /projects/my-site/change-sets --data '{"title": "Autumn refresh"}'
85
+ ```
86
+
87
+ The escape hatch for routes the commands above do not wrap yet. The method is
88
+ optional when it is `GET`, a leading `/v1` is accepted, and the API's response
89
+ envelope is passed through whole — with the same credential resolution, retries,
90
+ `--json` contract, and exit codes as every other command.
91
+
67
92
  ## Pin content to a release
68
93
 
69
94
  `myna.lock` records the release a repository builds against, so the same commit