silverwind 0bdf8f5bb3 wiki: accept plain text content instead of content_base64 (#156) ...

The `wiki_write` tool exposed the Gitea API's `content_base64` parameter directly, requiring callers to provide base64-encoded content. This caused LLM agents to incorrectly infer that other tools like `create_or_update_file` also require base64 encoding, corrupting files with literal base64 strings.

Rename the parameter to `content` (plain text) and handle base64 encoding internally, matching the pattern already used by `create_or_update_file`. Also added test coverage for this.

Closes #151

Reviewed-on: https://gitea.com/gitea/gitea-mcp/pulls/156
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-committed-by: silverwind <me@silverwind.io>

2026-03-14 01:49:40 +00:00

..

wiki_test.go

wiki: accept plain text content instead of content_base64 (#156)

2026-03-14 01:49:40 +00:00

wiki.go

wiki: accept plain text content instead of content_base64 (#156)

2026-03-14 01:49:40 +00:00