Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- GitHub added eight verified connectors, including Box and Supabase, on November 18. The public preview is available across Copilot plans.
- Connectors work locally and in cloud sandboxes. Copilot sessions running on GitHub Actions do not yet support them.
- If a connector fails in a supported session, check the organization's MCP policies, the connector URL, and the data the service account can access.
Find the GitHub-verified connector
GitHub announced eight new connectors on November 18, 2026, including Box and Supabase. Connectors are in public preview. In the Copilot desktop app, open Customize, select MCP, choose GitHub verified, and click Connect next to the service. In Copilot CLI, run <code>/mcp</code> and switch to Connectors. In VS Code, open Customizations from the Agents window.
If the service only has an install option, check whether you selected the GitHub-verified entry. GitHub's connector list provides the service name and its MCP URL. When reporting the issue, record the client version, GitHub account type, and service name.
After connecting, check where the current session runs
GitHub documents support in local sessions and Copilot sessions running in a cloud sandbox, including some started from GitHub.com. Actions-based Copilot sessions do not yet support connectors. Assigning a GitHub issue to Copilot is one example. Tasks started from the same page can run in different environments, so check the session or task details.
Using the same account in a supported session, try reading a Box test file you can access or listing a Supabase project you are authorized to use for testing. A read is enough. If the local session returns the expected item but the assigned-issue session cannot call the connector, check the runtime distinction first.
For a supported session, check organization and service access
Ask your administrator to check Editor preview features and MCP servers in Copilot for Copilot Business or Enterprise. Then check GitHub's policy support table for the rules enforced by your client. Clients enforcing Registry only block connectors. If enterprise managed settings include an allowlist, verify the exact connector URL against GitHub's list. A matching deny rule blocks access even when an allow entry matches.
The provider can require separate authorization. GitHub gives Box as an example where an administrator may need to enable Box MCP access first. After connecting, verify which workspace you signed into and whether your account can open the target file or project in the service itself. Give the responsible administrator the service name, target resource, and error status.
If Connecting persists, check the version and retest
The GitHub Copilot desktop app v1.4.0 release notes describe a display fix for newly added MCP servers that stayed on Connecting when the runtime never reported a status. If you see a similar symptom, check the version actually running, update through your organization's approved channel, and review the specific error shown in the app.
If a connected service is only missing one file or project, focus on access to that resource. If the service itself cannot connect, return to the organization policy and provider authorization checks. Keep the failure time and relevant error details, removing sign-in links, tokens, and unrelated private data before sharing.
Sources
Frequently Asked Questions
Can a GitHub issue assigned to Copilot use my connected Box account?
GitHub documents that Actions-based sessions do not yet support connectors. You can verify read access in an authorized local or cloud sandbox session.
Why does the connector fail when the enterprise allows its URL?
Check the rules enforced by your client and whether a deny rule matches. Then verify the service's own authorization requirements.
I updated the app and still can't see a Supabase project. What should I check?
Verify the signed-in account and access to the target project. Retest with an approved project in a supported session, then use the error status to check organization or service access.