StoreRouter Developer

ai.storerouterPublished by storerouter.aiOfficial publisherv1.0.0Updated Nov 5, 2026

Search and look up products across thousands of online stores, normalized into one schema.

The publisher's own server: StoreRouter

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant search and look up products across thousands of online stores, returned in one normalized schema.

What you can do
  • Search products across many online stores from a single query.
  • Look up individual products and compare listings returned in a normalized schema.
  • No tool list is published, so exact operations are not documented; capabilities are inferred from the registry description.
When to use it
Useful when an assistant needs product or price information spanning multiple retailers without integrating each store separately, for example shopping research or catalog comparison.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. OAuth authentication is required, so the user must sign in to a StoreRouter account through the OAuth flow. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth account, so review what the authorization grants before connecting. Queries about products are sent to a third-party service. No tool list is published, so confirm whether any tools write data or incur costs before relying on it.

Installation

In SourceWeft

  1. Open StoreRouter Developer in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.storerouter%2Fdeveloper/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "storerouter-developer": {
      "type": "http",
      "url": "https://mcp.dev.storerouter.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Storerouter integrations