How to Connect GitHub to Meta Muse — via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → GitHub, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

GitHub + Meta Muse

Work with GitHub from Claude, ChatGPT or Copilot through GitHub's official MCP server: read code and commits, search repositories, triage issues, and open and review pull requests.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

GITHUB_PAT

Step 1 — Get credentials

AnythingMCP connects to GitHub's official remote MCP server (https://api.githubcopilot.com/mcp/) with a personal access token. GitHub's server provides the tools: at install AnythingMCP reads the live tool list, and every tool gets the prefix github_. When GitHub adds tools, open the connector and click Discover tools.

1. On GitHub open Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token (direct link). Pick the resource owner (your account or an organization), an expiry, and Only select repositories with the repositories the AI should reach.
2. Under Repository permissions set Contents, Issues and Pull requests to Read-only, or to Read and write where the AI should create branches, commit, or open issues and pull requests. Metadata (read-only) is added automatically. For github_get_teams and github_get_team_members also add the organization permission Members: Read-only.
3. If the owner is an organization, an organization owner may have to approve the token first (the organization's Settings → Personal access tokens → Pending requests). Organizations with SAML single sign-on also need the token authorized for SSO.
4. Paste the token into GITHUB_PAT and install. A classic token (ghp_…, scope repo, plus read:org for teams) works too, but it reaches every repository you can, so a fine-grained token is the safer choice.

Organization policies: on Copilot Business or Copilot Enterprise, the MCP servers in Copilot policy must be enabled for the organization. Organizations can restrict personal access tokens, and enterprises with Enterprise Managed Users may have them disabled. For GitHub Enterprise Cloud with data residency, change the connector's base URL to https://copilot-api.<your-subdomain>.ghe.com/mcp. GitHub Enterprise Server has no hosted MCP server.

Toolsets and read-only mode: by default GitHub serves the context, repos, issues, pull_requests and users toolsets. To change that, add the header X-MCP-Toolsets in the connector editor (for example repos,issues,pull_requests,actions, or all), or X-MCP-Readonly: true to expose only read tools. Then click Discover tools.

Switched off at install: github_merge_pull_request, github_push_files, github_create_or_update_file and github_delete_file. Tools that a toolset header adds later, such as repository deletion, also arrive switched off. You can switch any of them on per tool in the connector. Everything runs as the token's owner, and issue and pull request text on public repositories is untrusted input (X-MCP-Lockdown: true hides content from authors without push access).

First call: github_get_me shows who the token belongs to; then use github_search_repositories, github_get_file_contents, github_list_issues and github_pull_request_read. A 401 means the token is wrong, expired or revoked; a 403 points to a missing permission, a pending organization approval or SSO authorization, or a policy; a 404 on a private repository usually means the token does not include it.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the GitHub tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

(showing 30 of 46 tools — install the connector to see them all)

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini