Omni Nli vs Twelve Permissions
A side-by-side look at the Omni Nli and Twelve Permissions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Omni Nli for developer tools work as a local process; choose Twelve Permissions for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Omni Nli when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Twelve Permissions when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 33/100 · Emerging | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 3 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Omni Nli | View Twelve Permissions |
Tools & capabilities
Omni Nli tools
No tool names declared yet. Check the project README from the listing page.
Twelve Permissions 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.
Omni Nli
{
"mcpServers": {
"omni-nli": {
"command": "uvx",
"args": [
"omni-nli"
]
}
}
}
Twelve Permissions
{
"mcpServers": {
"twelve-permissions": {
"url": "https://twelve-permissions.tsharpe.workers.dev/mcp"
}
}
}
Frequently asked questions
Omni Nli is categorized under Developer Tools and uses a local stdio subprocess. Twelve Permissions belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Omni Nli for developer tools work and Twelve Permissions for developer tools.
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.
Omni Nli has no declared pricing — check the project's own site. Twelve Permissions 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 omni-nli and twelve-permissions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Omni Nli has a quality signal of 33/100 (Emerging) with 2 views, 0 installs and 3 GitHub stars. Twelve Permissions has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.