Swiftsign MCP vs Runno
A side-by-side look at the Swiftsign MCP and Runno MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Swiftsign MCP for code execution work as a local process; choose Runno for code execution as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Swiftsign MCP when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
Choose Runno when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 40/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 775 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Swiftsign MCP | View Runno |
Tools & capabilities
Swiftsign MCP tools
No tool names declared yet. Check the project README from the listing page.
Runno tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Swiftsign MCP
{
"mcpServers": {
"mcp-43": {
"command": "npx",
"args": [
"-y",
"swiftsign-mcp"
]
}
}
}
Runno
{
"mcpServers": {
"runno": {
"command": "npx",
"args": [
"@runno/mcp"
]
}
}
}
Frequently asked questions
Swiftsign MCP is categorized under Code Execution and uses a local stdio subprocess. Runno belongs to Code Execution and uses a local stdio subprocess. Pick Swiftsign MCP for code execution work and Runno for code execution.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Swiftsign MCP has no declared pricing — check the project's own site. Runno has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-43 and runno as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Swiftsign MCP has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Runno has 48/100 (Fair) with 1 views, 0 installs and 775 GitHub stars.