-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Open
Description
Describe the bug
push_files calls are consistently slow (~1m12s–1m13s) in our MCP flow, even when one call fails with authorization error and the next call succeeds with the same payload.
This suggests significant latency before/around final Git operations, not only at final commit update step.
Affected version
Using hosted/remote GitHub MCP server, version: github-mcp-server/remote-57ddf9ca0de2f61fc022ca3cff21efc81a65fc99 (observed on 2026-03-08 via initialize -> serverInfo.version)
Steps to reproduce the behavior
- Call
github.push_fileswith a payload of 7 files (Twig templates + one largerclasses/Email.php) to: - First call result:
- Error:
failed to create tree: POST https://api.github.com/repos/Sogl/grav-plugin-login/git/trees: 403 Resource not accessible by personal access token [] - Client timing:
Worked for 1m 12s
- Error:
- Fix PAT permissions and call
github.push_filesagain with the same payload. - Second call result:
- Success, ref updated to commit: Sogl/grav-plugin-login@8be0cd1
- Client timing:
Worked for 1m 13s
Expected vs actual behavior
Expected:
- Latency in seconds for this payload size, or at least clear diagnostics if server-side queueing/throttling is involved.
Actual:
- Both failed and successful calls take ~70+ seconds with almost identical duration.
Logs
First call (failed, ~1m12s):
failed to create tree: POST https://api.github.com/repos/Sogl/grav-plugin-login/git/trees: 403 Resource not accessible by personal access token []
Second call (success, ~1m13s):
{"ref":"refs/heads/feature/multipart-emails", ... "sha":"8be0cd10415515109476025379545999f52b87b0"}
Request payload was the same large push_files body in both calls (7 files, full file contents).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels