Connect GitHub Copilot (VS Code)in three steps
GitHub Copilot (VS Code) reaches Pershot over MCP. Add the server and sign in, and it can quote first, then make videos with your credits, within the budget you set.
- Status
- Documented
- Tested by us
- Not yet
- Docs checked
Three stepsthen ask for a quote
Add Pershot to GitHub Copilot (VS Code)'s MCP settings file.
{ "servers": { "pershot": { "type": "http", "url": "https://mcp.pershot.app/mcp" } } }When GitHub Copilot (VS Code) asks, sign in to Pershot in your browser and allow the access.
Check it: ask GitHub Copilot (VS Code) for your Pershot credit balance, then for a quote before anything renders.
Start connecting GitHub Copilot (VS Code)See your AI connections in the studio
How itconnects
- MCP sign-inRecommendedSign in with your Pershot account in the browser (OAuth). No key is pasted into the agent.
- Connection codeA code you make under AI connections and paste into the agent's settings. It is sent as a header and spends your creative balance.
Good to know
In an organization or enterprise, an admin first has to turn on the MCP servers in Copilot policy.
GitHub Copilot (VS Code) docsBefore youconnect it
What does it spend?
Your creative balance, the same one the studio uses, within the budget you set. It quotes before each render. A render that makes no video, or whose result a safety check blocks, is refunded automatically; a video that is made is charged.
Who pays for GitHub Copilot (VS Code) itself?
GitHub Copilot (VS Code) has its own plans and model fees, paid to its maker. Pershot charges only for the videos and images it makes.
Can I take access away?
Yes. Revoke the connection under AI connections in the studio. It stops at once.
Has Pershot tested GitHub Copilot (VS Code)?
Not yet. The label comes from GitHub Copilot (VS Code)'s own documentation, checked on 2026-10-22. An agent we test ourselves will say Tested by us.