@farthershore/cli 0.3.9 → 0.3.11

package/README.md

@@ -14,6 +14,12 @@ Or use directly with npx:
 npx @farthershore/cli init my-api
 ```
 
+The package also ships an MCP stdio server for agents:
+
+```bash
+FARTHERSHORE_TOKEN=mk_xxx npx -p @farthershore/cli farthershore-mcp
+```
+
 ## Authentication
 
 Create an API token at [farthershore.com/settings/tokens](https://farthershore.com/settings/tokens), then:
@@ -34,6 +40,25 @@ export FARTHERSHORE_TOKEN=mk_xxx
 
 Tokens are stored in `~/.farthershore/credentials.json`.
 
+## Environment scope
+
+Most product commands can run against production or a named environment.
+Production is the default. `production`, `prod`, and `main` all mean the
+production scope.
+
+```bash
+farthershore env create preview --branch env/preview --format json
+farthershore env use preview --format json
+farthershore plan list --env preview --format json
+farthershore --env preview meter list --format json
+farthershore env run preview -- plan add pro --price-monthly 2900 --format json
+farthershore env use production --format json
+```
+
+`env use` is stored per product in `~/.farthershore/config.json`, so
+switching products does not accidentally carry the previous product's
+environment.
+
 ## Commands
 
 ### `farthershore init <name>`
@@ -77,6 +102,7 @@ the accepted config hash and GitHub sync state.
 
 ```bash
 farthershore product status --format json
+farthershore product status --env preview --format json
 ```
 
 ### `farthershore product config`
@@ -88,6 +114,7 @@ valid source of truth.
 ```bash
 farthershore product config --format json
 farthershore product config --format yaml
+farthershore product config --env preview --format json
 ```
 
 ### `farthershore product attempts`
@@ -98,6 +125,7 @@ product state.
 
 ```bash
 farthershore product attempts --format json
+farthershore product attempts --env preview --format json
 ```
 
 ### `farthershore meter`
@@ -114,6 +142,7 @@ farthershore meter add ai_tokens \
   --format json
 
 farthershore meter list --format json
+farthershore meter list --env preview --format json
 ```
 
 ### `farthershore feature`
@@ -126,6 +155,7 @@ farthershore feature add chat_completions \
   --format json
 
 farthershore feature bind chat_completions --plan pro --format json
+farthershore feature list --env preview --format json
 ```
 
 ### `farthershore plan`
@@ -147,6 +177,8 @@ farthershore plan add pro \
   --meter ai_tokens \
   --feature chat_completions \
   --format json
+
+farthershore plan list --env preview --format json
 ```
 
 ### `farthershore billing`
@@ -156,6 +188,7 @@ policy.
 
 ```bash
 farthershore billing strategy get --format json
+farthershore billing strategy get --env preview --format json
 
 farthershore billing strategy set prepaid_credits \
   --transition preserve_current_period \
@@ -174,6 +207,7 @@ subscribers before applying them.
 
 ```bash
 farthershore transition preview --format json
+farthershore transition preview --env preview --format json
 ```
 
 ### `farthershore validate [file]`
@@ -201,8 +235,23 @@ farthershore apply my-weather-api
 
 # Validate and remote-compile without applying
 farthershore apply --dry-run --format json
+farthershore apply --env preview --dry-run --format json
+```
+
+## MCP tools
+
+Run the MCP server with a maker token:
+
+```bash
+FARTHERSHORE_TOKEN=mk_xxx farthershore-mcp
 ```
 
+The MCP server exposes the same product-building workflow as the CLI:
+product create/status/config, environment list/create/use, billing strategy
+set, meter add, feature add, plan add, transition preview, and apply.
+Every tool accepts optional `product` and `env` fields where relevant and
+returns secret-free JSON.
+
 ### `farthershore set-key [token]`
 
 Set your API token. Interactive when run in a terminal, or pass the token as an argument for scripts.