Graviti vs Shopping Discovery
A side-by-side look at the Graviti and Shopping Discovery MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Graviti for e-commerce work as a local process; choose Shopping Discovery for e-commerce over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Graviti when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
Choose Shopping Discovery when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
PERISKOP_API_KEY. - You want tools like
run_shopping_discovery, get_discovery_result, discover_supported_stores.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 37/100 · Fair | 47/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 | PERISKOP_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Graviti | View Shopping Discovery |
Tools & capabilities
Graviti tools
No tool names declared yet. Check the project README from the listing page.
Shopping Discovery tools 5
run_shopping_discoveryFind, choose, browse, recommend, get the best product, or build a bundle from aget_discovery_resultRetrieve a previous result by `result_id`. Results are temporary and may expire.discover_supported_storesInspect the public stores Periskop can use. Returns public store capabilities only.report_result_feedbackReport whether a result was good, bad, or mixed.suggest_store_coverageSuggest a store/merchant/marketplace Periskop should support in the future. **Non-billable.**
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.
Graviti
{
"mcpServers": {
"graviti": {
"command": "npx",
"args": [
"-y",
"graviti-mcp"
]
}
}
}
Shopping Discovery
{
"mcpServers": {
"shopping-discovery": {
"url": "https://mcp.periskop.ai/v1/mcp"
}
}
}
Frequently asked questions
Graviti is categorized under E-Commerce and uses a local stdio subprocess. Shopping Discovery belongs to E-Commerce and uses a remote HTTP/SSE transport. Pick Graviti for e-commerce work and Shopping Discovery for e-commerce.
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.
Graviti has no declared pricing — check the project's own site. Shopping Discovery 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 graviti and shopping-discovery as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Graviti has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Shopping Discovery has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.