feat: add OAuth client flow with --auth flag - #131
Open
ishii-masaki-646 wants to merge 2 commits into
Open
Conversation
Add support for Gyazo OAuth authorization code grant flow as an alternative to setting GYAZO_ACCESS_TOKEN directly. Users can run `gyazo-mcp-server --auth` with GYAZO_CLIENT_ID and GYAZO_CLIENT_SECRET to authenticate via browser and store the token at ~/.gyazo-mcp/token.json. Token priority: GYAZO_ACCESS_TOKEN env var > stored OAuth token. Remove dummy GYAZO_ACCESS_TOKEN from Dockerfile. Update README with OAuth setup instructions and Docker volume mount examples. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Author
|
補足です。Motivation の 正しくは、Teams に限らず |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
gyazo-mcp-server --authで GYAZO_CLIENT_ID / GYAZO_CLIENT_SECRET を使ってブラウザ認証し、トークンを~/.gyazo-mcp/token.jsonに保存Motivation
Personal Access Token では自分がアップロードした画像しか取得できないが、OAuth クライアントフローを使うことで Gyazo Teams 内で共有された画像にもアクセス可能になる。
Test plan
GYAZO_ACCESS_TOKENのみで従来通り動作することを確認--authフラグで OAuth フローが正常に完了しトークンが保存されることを確認🤖 Generated with Claude Code