Cinderwright API vs Orbis MCP
A side-by-side look at the Cinderwright API and Orbis MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cinderwright API for aggregators work as a local process; choose Orbis MCP for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cinderwright API when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CW_KEY.
Choose Orbis MCP when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ORBIS_KEY. - You want tools like
browse_apis, call_api, register_agent.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 43/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | CW_KEY | ORBIS_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Cinderwright API | View Orbis MCP |
Tools & capabilities
Cinderwright API tools
No tool names declared yet. Check the project README from the listing page.
Orbis MCP tools 4
browse_apisSearch and list available APIs on Orbiscall_apiCall any API — x402 payment handled automaticallyregister_agentRegister your agent wallet for trackingsubscribe_to_apiSubscribe to an API for discounted access
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.
Cinderwright API
{
"mcpServers": {
"cinderwright-ai-cinderwright-api": {
"command": "npx",
"args": [
"-y",
"cinderwright"
],
"env": {
"CW_KEY": "YOUR_CW_KEY_HERE"
}
}
}
}
Orbis MCP
{
"mcpServers": {
"orbis-mcp": {
"command": "npx",
"args": [
"-y",
"@orbisapi/mcp"
],
"env": {
"ORBIS_KEY": "YOUR_ORBIS_KEY_HERE"
}
}
}
}
Frequently asked questions
Cinderwright API is categorized under Aggregators and uses a local stdio subprocess. Orbis MCP belongs to Aggregators and uses a local stdio subprocess. Pick Cinderwright API for aggregators work and Orbis MCP for aggregators.
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.
Cinderwright API is listed as freemium — a free tier with paid plans. Auth: api key required. Orbis MCP 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 cinderwright-ai-cinderwright-api and orbis-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cinderwright API has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 4 GitHub stars. Orbis MCP has 51/100 (Good) with 0 views, 0 installs and 2 GitHub stars.