FlashDuty MCP Server 0.9.15

What's new

• OAuth sign-in for remote MCP clients. The HTTP transport now accepts Flashduty OAuth access tokens in addition to app keys. Clients that implement the MCP authorization spec (for example Claude, ChatGPT and Claude Code) can connect to https://mcp.flashcat.cloud/mcp, discover the authorization server from the protected resource metadata, and sign in through the Flashduty consent page. App-key authentication is unchanged.
• Correct resource URL behind TLS-terminating load balancers. The protected resource metadata (RFC 9728) now advertises an https resource for non-loopback hosts when the proxy does not send X-Forwarded-Proto, so OAuth clients no longer reject the advertised resource.
• Depends on go-flashduty v0.15.11.

Changelog

• a26326a fix(server): advertise an https resource behind TLS-terminating load balancers
• 35e01de ci(docker): build without the GitHub Actions layer cache
• 7165b0c chore: depend on go-flashduty v0.15.11
• 1253695 ci(lint): use the go.mod Go version like the other workflows
• 6f2cc6f build(deps): bump go-flashduty for access-token client
• d831db1 feat(server): accept OAuth access tokens on the HTTP transport
• 7616fb3 docs: point to flashduty-cli for full open-API coverage (#73)