DATPAQ vs Marketplace
A side-by-side look at the DATPAQ and Marketplace MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MarketplaceAggregatorsSearch the JoJ API marketplace, read endpoint docs, and call any API with one key via one gateway.37FairAuth: not declaredVerdict: choose DATPAQ for aggregators work over a hosted endpoint; choose Marketplace for aggregators. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose DATPAQ when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
DATPAQ_BASE_URL, PORT.
MChoose Marketplace when
- You need dedicated capabilities in the Aggregators domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Marketplace | |
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 35/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DATPAQ_BASE_URLPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View DATPAQ | View Marketplace |
Tools & capabilities
DATPAQ tools
No tool names declared yet. Check the project README from the listing page.
Marketplace 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.
DATPAQ
{
"mcpServers": {
"datpaq": {
"url": "https://mcp.datpaq.com/"
}
}
}
Marketplace
No confirmed install command for Marketplace yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
DATPAQ is categorized under Aggregators and uses a remote HTTP/SSE transport. Marketplace belongs to Aggregators and uses an install path we have not confirmed yet. Pick DATPAQ for aggregators work and Marketplace 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. Marketplace has no confirmed install command yet — follow its own setup instructions.
DATPAQ has no declared pricing — check the project's own site. Marketplace 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 datpaq and marketplace-7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DATPAQ has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Marketplace has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.