docs(readme): state env var auth direction in the config table #28

Merged

David merged 2 commits from docs/YTMCP-22-env-var-direction into main

2026-06-25 10:27:27 +02:00

David commented

2026-06-23 12:35:58 +02:00

Owner

Problem

The stdio Configuration table documented YOUTRACK_TOKEN as "Permanent API token used to authenticate" without stating direction. A reader cannot tell whether it authenticates the server to YouTrack or a client to the server. Operators coming from forgejo-mcp (whose MCP_HTTP_TOKEN is an inbound client-to-server bearer) misread YOUTRACK_TOKEN as the same kind of token.

Change

Documentation only. Added a Direction column and rewrote the rows so each stdio variable names its direction: YOUTRACK_BASE_URL and YOUTRACK_TOKEN are server-to-YouTrack (upstream), and YOUTRACK_TOKEN is the token the server presents to YouTrack, not an inbound bearer. Added a note that stdio has no inbound auth (the launching MCP client owns the process over stdin/stdout) and that no MCP_HTTP_TOKEN-style inbound bearer exists here; inbound per-user auth lives only in the http transport via OAuth 2.1 against Hub.

No new environment variables. just pre-commit (fmt, clippy, build, 73 tests) passes.

#YTMCP-22

## Problem The stdio Configuration table documented `YOUTRACK_TOKEN` as "Permanent API token used to authenticate" without stating direction. A reader cannot tell whether it authenticates the server to YouTrack or a client to the server. Operators coming from `forgejo-mcp` (whose `MCP_HTTP_TOKEN` is an inbound client-to-server bearer) misread `YOUTRACK_TOKEN` as the same kind of token. ## Change Documentation only. Added a Direction column and rewrote the rows so each stdio variable names its direction: `YOUTRACK_BASE_URL` and `YOUTRACK_TOKEN` are server-to-YouTrack (upstream), and `YOUTRACK_TOKEN` is the token the server presents to YouTrack, not an inbound bearer. Added a note that stdio has no inbound auth (the launching MCP client owns the process over stdin/stdout) and that no `MCP_HTTP_TOKEN`-style inbound bearer exists here; inbound per-user auth lives only in the http transport via OAuth 2.1 against Hub. No new environment variables. `just pre-commit` (fmt, clippy, build, 73 tests) passes. #YTMCP-22

David added 1 commit

2026-06-23 12:35:58 +02:00

docs(readme): state env var auth direction in the config table

Check / fmt + clippy + build + tests (pull_request) Successful in 21s

Details

4d8f0feb6d

The stdio Configuration table documented YOUTRACK_TOKEN as "Permanent API token used to authenticate" without saying which direction it authenticates, so a reader could not tell whether it was the server authenticating to YouTrack or a client authenticating to the server. Operators arriving from forgejo-mcp (whose MCP_HTTP_TOKEN is an inbound client-to-server bearer) misread YOUTRACK_TOKEN as the same kind of token.

Add a Direction column and rewrite the rows: YOUTRACK_BASE_URL and YOUTRACK_TOKEN are server-to-YouTrack (upstream), and YOUTRACK_TOKEN is the token the server presents to YouTrack, not an inbound bearer. Add a note that stdio has no inbound auth (the launching client owns the process) and that no MCP_HTTP_TOKEN-style inbound bearer exists; inbound per-user auth lives only in the http transport via OAuth 2.1 against Hub.

Signed-off-by: David Randall <David@NiceGuyIT.biz>

#YTMCP-22

David added 1 commit

2026-06-25 10:26:04 +02:00

Merge branch 'main' into docs/YTMCP-22-env-var-direction

Check / fmt + clippy + build + tests (pull_request) Successful in 22s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

075beec2e2