# GitHub MCP Server Status

Is the GitHub MCP server up? Live check of api.githubcopilot.com, plus the fixes that solve most connection problems.

URL: https://shortformkit.com/github-mcp-status/
Updated: 2026-10-14

**The check above sends the official GitHub MCP endpoint https://api.githubcopilot.com/mcp the first request every MCP client sends. Up with HTTP 401 is the normal state: the server answers and asks for sign-in. If it is up and your connector still fails, work through the fixes below.**

| MCP server URL | https://api.githubcopilot.com/mcp |
|---|---|
| Transport | Streamable HTTP |
| Authentication | OAuth sign-in |
| Product | [GitHub](https://github.com) |

## GitHub MCP not working? Fix it in this order

- **Look at the live check above.** If it says Down, the problem is on GitHub's side and usually clears up on its own; check again in a few minutes.
- **Use the current URL**: https://api.githubcopilot.com/mcp.
- **Sign in again.** GitHub uses OAuth: tokens expire or get revoked when you change your password, leave a workspace or an admin removes access. Remove the connector and add it again, then finish the sign-in in the browser window that opens. In Claude Code: claude mcp remove github and claude mcp add --transport http github https://api.githubcopilot.com/mcp, then claude mcp list to see the state.
- **Ask your admin.** In team and company workspaces an admin may have to allow the integration for GitHub before members can connect.
- **Check the network.** VPNs, company proxies and firewalls can block api.githubcopilot.com. Try another network to rule it out.
- **Update the client.** Older clients only speak stdio or the old SSE transport. Current Claude, ChatGPT, Cursor and VS Code versions support remote servers over HTTP.
- **Test it outside your client.** Paste the URL into our [MCP Server Tester](https://shortformkit.com/mcp-server-tester/?url=https://api.githubcopilot.com/mcp) to see exactly what the server answers.

## Add GitHub MCP to your client

**Claude (claude.ai, desktop):** Customize, Connectors, + Add, Add custom connector, paste https://api.githubcopilot.com/mcp. **Claude Code:** claude mcp add --transport http github https://api.githubcopilot.com/mcp. **Cursor:** { "mcpServers": { "github": { "url": "https://api.githubcopilot.com/mcp" } } }. **VS Code:** { "servers": { "github": { "type": "http", "url": "https://api.githubcopilot.com/mcp" } } }.

Status of the other servers: [MCP server status overview](https://shortformkit.com/mcp-server-status/).

## How it works

1. **Check the live status** Up, including HTTP 401, means the server answers.
2. **Use the current URL** https://api.githubcopilot.com/mcp
3. **Reconnect** Remove the connector, add it again and sign in.

## FAQ

**Is GitHub MCP down right now?**
The live check at the top of this page tests https://api.githubcopilot.com/mcp at most every five minutes. Up, including HTTP 401, means the server is answering.

**What is the GitHub MCP server URL?**
https://api.githubcopilot.com/mcp.

**Why is GitHub MCP not working in Claude or Cursor?**
Most often an expired or revoked sign-in, an outdated URL or a blocked network. Remove the connector, add it again with the current URL and sign in again.

**Why does GitHub MCP return 401?**
Without a valid token every request gets 401, which is how the client knows it has to sign in. If you see 401 after signing in, the token expired or was revoked; reconnect.


Source: Shortform Kit (https://shortformkit.com/github-mcp-status/). Free, no login.