Use eSign 360 e-signatures in VS Code
Add the eSign 360 MCP server to VS Code and let GitHub Copilot chat prepare documents, send them for signature after you confirm, and report who has signed.
In short
- What it is: a remote MCP server for legal e-signatures, built into eSign 360 by 360 SaaS Pty Ltd, an Australian company.
- Server address:
https://admin.esign360.ai/mcp - Works with: Visual Studio Code with GitHub Copilot chat. VS Code can add remote HTTP MCP servers from the command palette or an
mcp.jsonfile. - Price: AI assistant access is A$10 a month plus GST on the API plan, charged only while it is on. eSign 360 is free for Portal 360 customers, and the free tier is 5 documents a month.
- Control: VS Code asks before it sends, and every action is in your audit log.
How to connect eSign 360 to VS Code with GitHub Copilot
Before you start:
- On the eSign 360 API plan, an administrator switches on AI assistant access in Settings. It is A$10 a month plus GST, charged only while it is on.
- You sign in with your own eSign 360 account, so the assistant acts as you and your permissions apply.
Then:
- In VS Code, open the Command Palette and run MCP: Add Server.
- Choose HTTP (HTTP or Server-Sent Events) and enter
https://admin.esign360.ai/mcp. - Enter a server ID such as
esign360and choose where to save it (global for all workspaces). - Review and accept the server trust prompt, then sign in to eSign 360 when VS Code opens your browser and press Allow.
- Open Copilot chat and ask: “List my documents that are waiting for a signature.”
{
"servers": {
"esign360": {
"type": "http",
"url": "https://admin.esign360.ai/mcp"
}
}
}The JSON above is what the guided flow writes to your mcp.json. Share it with your team in a workspace .mcp.json if everyone should have the connector, and keep any credentials out of shared files. eSign 360 uses sign-in, so none are needed.
What you can ask VS Code with GitHub Copilot to do
| Ask | What happens |
|---|---|
| “Send the attached NDA to sam@acme.com.” | It prepares the document and shows you the signers. Nothing is emailed until you say yes. |
| “Which documents are still waiting?” | It lists your documents and their status. |
| “Remind everyone who has not signed.” | It sends reminders to the outstanding signers. |
| “Cancel the lease renewal.” | It voids the document. |
| “Get me the signed copy.” | It returns a link to the signed PDF or audit certificate that expires in 10 minutes. |
The full list of tools is on the MCP server page. Signatures are legally recognised in Australia, and every signed document carries a tamper-evident certificate of completion. See are electronic signatures legal in Australia.
Questions about VS Code with GitHub Copilot and eSign 360
Where does VS Code store the server?
In a global MCP configuration for your user, or a workspace file if you choose to share it with a team.
Is the eSign 360 server safe to trust?
Review VS Code’s trust prompt before accepting. eSign 360 acts only as the signed-in user, asks before it sends, and records every action in the audit log.
Does it work with other editors?
Any editor or tool that supports remote MCP servers with OAuth sign-in can use the same address.
Connect other assistants
- Claude
- ChatGPT
- Grok
- Microsoft Copilot Studio
- Cursor
- Claude Code
- Gemini CLI
- All AI assistants and the full tool list
Source for the VS Code with GitHub Copilot steps: VS Code documentation: MCP servers. Menus and labels can change, so check the vendor’s documentation if a step looks different.