GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://swiftsign.ca/mcpRun this in your terminal
claude mcp add --transport http swiftsign https://swiftsign.ca/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"swiftsign": {
"url": "https://swiftsign.ca/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://swiftsign.ca/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain swiftsign.ca (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.5.2) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server for SwiftSign — send documents for e-signature directly from Claude Code.
Add to your .mcp.json (Claude Code config):
{
"mcpServers": { "swiftsign": { "command": "npx", "args": ["-y", "swiftsign-mcp"], "env": { "SWIFTSIGN_API_KEY": "sk_your_api_key" } } } }
Get your API key at swiftsign.ca/dashboard — or skip the browser entirely and call swiftsign_signup to mint a sandbox key (see below).
SwiftSign keys come in two flavors:
sk_test_. Everything works (send, status, templates, embedded URLs) but documents are test sends. No card needed.swiftsign_upgrade (a Stripe pay link the dev opens to add a card).The same tools work in both modes; the mode is determined by the key in SWIFTSIGN_API_KEY.
An agent can go from zero to a live e-signature without ever opening a dashboard:
sk_test_ key back. Set it as SWIFTSIGN_API_KEY.swiftsign_send_from_template) — send a test document and watch the full flow work.swiftsign_signup is the only tool that works without a key set — it's how you get one.
| Tool | Description |
|---|---|
swiftsign_signup | Create a sandbox account and get a test API key (no browser) |
swiftsign_send_envelope | Send document(s) for e-signature |
swiftsign_send_from_template | Send an envelope from a saved template by role |
swiftsign_check_status | Check envelope signing status |
swiftsign_list_envelopes | List all sent envelopes |
swiftsign_list_templates | List your saved templates |
swiftsign_create_embedded_url | Mint a short-lived embedded signing URL |
swiftsign_void_envelope | Cancel an envelope |
swiftsign_upgrade | Get a Stripe pay link to upgrade to PRO (live sends) |
Once configured, just ask Claude:
"Send this contract to john@acme.com for signing"
Claude will use SwiftSign to send the document, place signature fields, and email the recipient a signing link.
"Send the MSA at data/contracts/generated/Acme_MSA.pdf to John Smith (john@acme.com) for signing, with a signature field at the bottom"
SwiftSign handles:
SwiftSign e-signatures are legally binding under: