outrank-cli 0.6.0-rc.1 → 0.6.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 +3 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -212,10 +212,11 @@ A selected profile ignores `OUTRANK_API_KEY`, so both servers stay on their own
|
|
|
212
212
|
### Troubleshooting
|
|
213
213
|
|
|
214
214
|
- **The server does not start.** Run the same command in a terminal: `npx -y outrank-cli@0.6.0 mcp --help` must print usage. On native Windows, clients need the `cmd /c npx …` form.
|
|
215
|
-
- **
|
|
215
|
+
- **PowerShell reports `unknown option '-y'` on `claude mcp add`.** PowerShell drops the `--` separator when `claude` is a script or a function instead of the program itself (an npm-installed Claude Code, or a wrapper in your profile). Call `claude.exe mcp add …` or run the command from the Command Prompt.
|
|
216
|
+
- **The first start is slow, or the server fails to connect.** `npx` downloads the package the first time and contacts the npm registry on every start, so an empty cache or a slow registry can push startup past the client's limit. In Claude Code, run `/mcp reconnect all` to try again; `MCP_TIMEOUT` (milliseconds) raises the startup limit. To take the registry out of the startup path, install the package globally (`npm install -g outrank-cli@0.6.0`) and use `outrank-cli mcp` as the command.
|
|
216
217
|
- **Every call returns `CLI_AUTH_REQUIRED`.** The server has no key. Add `OUTRANK_API_KEY` to the server entry, or select a stored profile with `--profile`.
|
|
217
218
|
- **Only a few tools are listed.** Read the server instructions in the client: they name the toolsets that are off and why. See [Toolsets](#toolsets).
|
|
218
|
-
- **A long call times out.** `improvements_analyze`, `improvements_candidates_brief`, `improvements_tasks_execute`, `improvements_executions_push`, `articles_generate`, `articles_precreate`, `articles_retry_publish` and `keywords_generate` can run for minutes. When the call does not finish, the result is `CLI_OPERATION_MAY_STILL_BE_RUNNING` and names the tool to poll: the work continues on the server, so poll instead of repeating the call. The server sends progress notifications while such a call runs, but clients do not have to extend their own limit because of them.
|
|
219
|
+
- **A long call times out.** `improvements_analyze`, `improvements_candidates_brief`, `improvements_tasks_execute`, `improvements_executions_push`, `articles_generate`, `articles_precreate`, `articles_retry_publish` and `keywords_generate` can run for minutes. When the call does not finish, the result is `CLI_OPERATION_MAY_STILL_BE_RUNNING` and names the tool to poll: the work continues on the server, so poll instead of repeating the call. The server sends progress notifications while such a call runs, but clients do not have to extend their own limit because of them. Claude Code does not cut a tool call off by default: `MCP_TOOL_TIMEOUT` (milliseconds) is about 28 hours when unset, and a `timeout` field on the server's `.mcp.json` entry sets a hard limit for that server which progress notifications do not extend. Cursor (measured on 3.22) stops a call after 120 seconds without a progress notification and keeps waiting while they arrive, so long calls get through there. Other clients may stop after a fixed time whatever the server does; the poll tools are the way through.
|
|
219
220
|
- **The client warns about too many tools.** Some clients cap or warn above a few dozen tools. Narrow the list with `--toolsets`, for example `--toolsets core,keywords,articles`.
|
|
220
221
|
- **Staging or a local deployment.** Store a profile for it in a terminal (see [Security](#security)) and start the server with `--profile <name>`.
|
|
221
222
|
- **See what the server does.** Set `OUTRANK_MCP_DEBUG=1`; one line per tool call is written to stderr, which the client shows in its MCP logs.
|