GitHub Copilot
Agent mode, on your real project. You approve the send.
GitHub Copilot reaches your project through the MCP server in agent mode and in the Copilot CLI: it checks the data your code produces, answers with real figures and prepares the segment or the campaign. The cloud agent on github.com takes static headers only, so there it connects with an organization API key. Sending waits for you.
GitHub Copilot, working on a real project
~/acme/instasent [⎇ reports]Auto
Connect GitHub Copilot to your project
The fast way. Paste this prompt into GitHub Copilot and it does the three steps for you.
Or do it by hand:
- 1
Add the server
In VS Code, run MCP: Add Server from the Command Palette, choose HTTP and paste Instasent's server address. In the Copilot CLI, it is /mcp add.
- 2
Sign in
Start the server and sign in when asked. Copilot opens Instasent in your browser: sign in, pick the project and the permissions it gets. The connection is listed under Connected apps, and you can revoke it any time.
- 3
Check it
In agent mode, ask it to count your contacts. If the figure matches your project, you are connected.
What to ask GitHub Copilot
- Which attributes does our signup form send that are not in my audience yet?
- Look at the event this pull request adds and tell me if it is already arriving in Instasent.
- Build a segment with the contacts that event would catch and tell me how many there are.
- Prepare the campaign draft for them and leave it for me to review.
What GitHub Copilot will not do on its own
- It reads everything.
- Audience, campaigns, flows and results of the project you connect.
- It creates and leaves it ready.
- Segments and campaign drafts, prepared for you to review.
- It never sends.
- Sending waits for your approval, every time. No agent sends on its own.