GitHub¶
Artific Connect ยท GitHub gives a key GitHub's own tools: issues, pull requests, code search and the rest of what a repository can be asked. It installs from the Marketplace like any other bundle.
What you get¶
One toolset, github, holding everything GitHub's own MCP server offers, plus a skill that tells
the model how a repository is named and what to ask you for. Attach the toolset to a key and the
tools are there.
Signing in¶
The tools act as the person the turn is for, through that person's own GitHub account โ so a turn sees exactly what that person may see, and nothing else. Two things follow:
- a request must name a
user; one that names nobody is told so instead of calling a tool; - each person signs in once, from the bundle's page in the console or through the link the model is given the first time it tries.
The consent screen says Artific: the application is this deployment's, registered once by its operator, and no organisation registers one of its own.
Before it works¶
Your administrator has to allow the hosts the bundle dials in the key's own egress policy:
api.githubcopilot.comโ the MCP server itself;github.comโ where a person signs in and where the code is exchanged for a token.
If the operator has not registered the Artific application at GitHub yet, the install waits: the bundle sits at needs configuration and names what it is waiting for.
Good to know¶
- Some of GitHub's toolsets are only available on a paid Copilot plan; a tool that answers "not available" for that reason is GitHub's decision, not Core's.
- Rate limits are per person and reset within the hour.
- Verified 2026-09-24 from the design record: the server is
https://api.githubcopilot.com/mcp/and sign-in runs overgithub.com/login/oauth. What one smoke test with a real application confirms will be recorded here with its date. - The mark: this bundle's card uses GitHub's own Invertocat mark, from its logo kit, under GitHub's logo guidelines, which permit the mark "indicating integration with GitHub" (checked 2026-09-24).