[Question] Working with GitHub MCP output in GoClaw — file content not accessible

Context

I'm trying to use GoClaw to work with files and code fetched via the GitHub MCP, but I'm running
into several cases where the output isn't usable. Listing them below in case these are known
limitations or there's a recommended workaround.

Issue 1: Single file returns EmbeddedResource with no content

When fetching a single file via the GitHub MCP, the result comes back as an EmbeddedResource
type — The content is effectively inaccessible.

Issue 2: Folder listing returns redacted temporary URLs

When fetching a folder/tree, the GitHub MCP returns a list of files with temporary signed tokens
in the URLs — but GoClaw redacts these links, apparently for security reasons.

Environment

• GoClAW version: 3.7.0

Any guidance on the intended API contract for MCP EmbeddedResource handling, and the recommended
pattern for codebase-scale file access, would be greatly appreciated.

Review the GoClaw v3.7.0 MCP integration entry points for GitHub single-file and folder/tree responses, focusing on EmbeddedResource handling and URL redaction. Compare the observed output with the intended MCP API contract; done means the supported behavior or workaround for codebase-scale access is documented or the inaccessible content and redacted URLs are made usable.