# GitHub plugin Cloud environment fails - empty cloud-plugin-manifest.json, Local connects fine

**URL:** <https://forum.cursor.com/t/github-plugin-cloud-environment-fails-empty-cloud-plugin-manifest-json-local-connects-fine/170778>\
**Category:** Bug Reports\
**Tags:** mcp, plugins, github, automations, cloud-agents\
**Created:** [September 6, 2026, 11:52am UTC](https://forum.cursor.com/t/github-plugin-cloud-environment-fails-empty-cloud-plugin-manifest-json-local-connects-fine/170778 "2026-09-06T11:52:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![joshjames](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@joshjames](https://forum.cursor.com/u/joshjames)\
**Post date:** [September 6, 2026, 11:52am UTC](https://forum.cursor.com/t/github-plugin-cloud-environment-fails-empty-cloud-plugin-manifest-json-local-connects-fine/170778/1 "2026-09-06T11:52:35Z")

</div>

### Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

### Describe the Bug

The GitHub marketplace plugin’s Cloud environment fails to connect while Local connects fine using the same PAT. Cloud fails with Streamable HTTP error: Error POSTing when it tries to handshake with [https://api.githubcopilot.com/mcp/](https://api.githubcopilot.com/mcp/). This blocks any Cursor Automation that depends on it — in my case, a custom “Security & Production-Impact Review” automation.

I found ~/.cursor/plugins/cache/.cloud-plugin-manifest.json is empty — {“plugins”:,…}, with a digest that’s literally the SHA-256 hash of an empty string. So no plugin credentials appear to have ever synced to Cloud, despite Local having a working, authenticated connection.

### Steps to Reproduce

Configure the GitHub marketplace plugin with a PAT via Dashboard → Plugins → GitHub → Configure  
Confirm Local environment connects (it does — 44 tools registered, get\_me resolves)  
Check the plugin’s Cloud environment status, or try using it as a tool in a Cursor Automation

### Expected Behavior

Cloud environment connects using the same synced PAT credentials as Local.

### Operating System

MacOS

### Version Information

Cursor 3.19.13, macOS 26.6.2

### For AI issues: which model did you use?

N/A - Plugin/MCP connectivity issue, not a model behaviour issue.

### For AI issues: add Request ID with privacy disabled

581d26df-b38f-4609-819d-b8807ad6d882

### Additional Information

Already tried, none of which fixed it: Retry/Reload on the Cloud environment; Disconnect on the automation’s GitHub tool (only cleared local OAuth housekeeping, unrelated to the PAT-based auth this plugin actually uses); quitting and reopening the app; re-saving the PAT in Dashboard → Plugins → GitHub → Configure (manifest stayed empty afterward); setting up Cloud Agents (Dashboard → Overview → “Set up cloud for faster, parallelized agents”) in case that was a missing prerequisite (manifest still empty afterward, no change).

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [September 8, 2026, 10:36am UTC](https://forum.cursor.com/t/github-plugin-cloud-environment-fails-empty-cloud-plugin-manifest-json-local-connects-fine/170778/9 "2026-09-08T10:36:02Z")

</div>

Hey @joshjames!

I tested this exact setup on a fresh account (GitHub plugin, token saved under Configure, cloud agent started from the Agents window and from [cursor.com/agents](http://cursor.com/agents)) and the GitHub tools work in the cloud, so the saved token is being applied there.

1. Open [cursor.com/agents](http://cursor.com/agents), then the menu \> MCP Servers (or in the app: Settings \> MCP \> Cloud tab).
2. Look for any GitHub entry that is NOT the one coming from the plugin, for example, one you added by hand or one that shows a Connect / Disconnect button. If you see one, remove it.
3. Go to Dashboard \> Plugins \> GitHub \> Configure, paste your token again and save.
4. Start a new cloud agent from [cursor.com/agents](http://cursor.com/agents) on any repo and ask it: “Use the GitHub MCP get\_me tool and tell me my GitHub username.”
5. Does step 4 return your username? If yes, add the plugin’s GitHub server back into your automation’s tools, save it, and run it once.

---

<div class="post-metadata">

**Author:** ![joshjames](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@joshjames](https://forum.cursor.com/u/joshjames)\
**Post date:** [September 9, 2026, 4:56pm UTC](https://forum.cursor.com/t/github-plugin-cloud-environment-fails-empty-cloud-plugin-manifest-json-local-connects-fine/170778/10 "2026-09-09T16:56:41Z")

</div>

Thanks @Colin

Ran this as suggested and everything is now working correctly.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [September 11, 2026, 4:56pm UTC](https://forum.cursor.com/t/github-plugin-cloud-environment-fails-empty-cloud-plugin-manifest-json-local-connects-fine/170778/11 "2026-09-11T16:56:54Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
