Improve redMCP server operations
This commit is contained in:
+35
-5
@@ -99,6 +99,12 @@ For local network testing, run the Streamable HTTP server:
|
||||
MCP_SERVER_TOKEN=test-token redMCP/bin/redmcp-http-server.php --host 0.0.0.0 --port 8765
|
||||
```
|
||||
|
||||
Generate a bearer token with:
|
||||
|
||||
```sh
|
||||
redMCP/bin/generate-bearer-token.php --env-line
|
||||
```
|
||||
|
||||
The network endpoint defaults to `/mcp` and requires:
|
||||
|
||||
```text
|
||||
@@ -115,6 +121,30 @@ curl -sS \
|
||||
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
|
||||
```
|
||||
|
||||
HTTP server process helpers:
|
||||
|
||||
```sh
|
||||
redMCP/bin/redmcp-http-server.php --status
|
||||
redMCP/bin/redmcp-http-server.php --stop
|
||||
redMCP/bin/redmcp-http-server.php --pid-file /tmp/redmcp-http-server.pid --status
|
||||
```
|
||||
|
||||
The default PID file is `/tmp/redmcp-http-server.pid`. A second server start
|
||||
fails if the PID file points to a live process. Use `--force` only to replace a
|
||||
stale PID file.
|
||||
|
||||
Debug logging is disabled by default. To record full MCP params/tool arguments
|
||||
as JSONL during local testing:
|
||||
|
||||
```sh
|
||||
MCP_SERVER_TOKEN=test-token redMCP/bin/redmcp-http-server.php \
|
||||
--debug-log /tmp/redmcp-mcp.log
|
||||
```
|
||||
|
||||
Debug logs may include customer text, issue notes, search terms, email content,
|
||||
and IDs. Authorization headers, bearer tokens, and Redmine API keys are not
|
||||
logged.
|
||||
|
||||
Example stdio client configuration:
|
||||
|
||||
```json
|
||||
@@ -127,11 +157,11 @@ Example stdio client configuration:
|
||||
}
|
||||
```
|
||||
|
||||
Both transports expose tools for native Redmine filtering/search, issue CRUD,
|
||||
Helpdesk-aware issue reads, and explicit Helpdesk email responses. Tools that
|
||||
can send customer-visible mail require an explicit tool call such as
|
||||
`redmine_send_helpdesk_response` or `redmine_update_issue` with
|
||||
`send_helpdesk_email=true`.
|
||||
Both transports expose tools for native Redmine project listing/detail,
|
||||
filtering/search, issue CRUD, Helpdesk-aware issue reads, and explicit Helpdesk
|
||||
email responses. Tools that can send customer-visible mail require an explicit
|
||||
tool call such as `redmine_send_helpdesk_response` or `redmine_update_issue`
|
||||
with `send_helpdesk_email=true`.
|
||||
|
||||
## Test instance
|
||||
|
||||
|
||||
Reference in New Issue
Block a user