A side-by-side look at the Iconic CLS and Trident MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Iconic CLS for developer tools work; choose Trident MCP for multimedia process. You can also run both side by side in one mcpServers block.
TRIPO_API_KEY.Rows where the two servers differ are marked.
| Spec | I Iconic CLS | |
|---|---|---|
| Category | Developer Tools | Multimedia Process |
| Quality signal | 37/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Iconic CLS yet — follow the setup steps linked from its listing page rather than a guessed package name.
No confirmed install command for Trident MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
TRIPO_API_KEY| Verified owner | Community listing | Community listing |
|---|
| GitHub stars | — | 5 |
|---|
| Directory activity | 0 views 0 installs 0 upvotes | 26 views 10 installs 5 upvotes |
|---|
| Tools | Not listed | Not listed |
|---|
| Full listing | View Iconic CLS | View Trident MCP |
|---|