How to Use the Searchspring MCP in Claude Code

Q: Can I use Claude Code to debug Searchspring redirect rules?

Yes. You can ask the agent to trigger the MCP tool searchcustom with specific query terms to inspect the raw Searchspring API response and verify if redirects or custom parameters are triggering.

Query, test, and script your Searchspring catalog directly from the command line using Claude Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Searchspring MCP to Claude Code

Create your Vinkius account to connect Searchspring to Claude Code — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Searchspring with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Command-line Searchspring diagnostics

Claude Code lets you inspect your search engine using this MCP server directly from the terminal. You can run quick CLI commands to call `search_products` and review raw Searchspring JSON payloads instantly. This is perfect for debugging Searchspring relevance or verifying that newly indexed items are showing up in search results without having to open a browser.

Automate catalog health checks via MCP Server

You can write shell scripts that use the Claude Code terminal agent to verify your catalog health. The agent calls `search_sku` for key products to ensure they return valid Searchspring pricing and inventory data. If a critical Searchspring SKU returns an error or empty data, the script can pipe that output to your alerting system or log it for immediate review.

Inspect Searchspring filters and facets from the CLI

Verify your filtering rules by telling Claude Code to call `search_filtered` with specific attributes. It returns the exact Searchspring facet counts, letting you verify that your merchandising rules are working. You can also test price filters by running `search_price_range` to make sure your Searchspring pricing tiers map correctly to the active search index.

Setup guide

Set up Searchspring MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see searchspring-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Searchspring transactions." It will automatically discover and invoke the available Searchspring tools.

Terminal

claude mcp add --transport http searchspring-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Searchspring MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "searchspring-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Searchspring. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Searchspring now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Searchspring MCP in Claude Code

You ask the Claude Code agent to search for a term. It invokes `search_products` behind the scenes and prints the matching Searchspring items directly to your terminal.

Yes. You can ask the agent to trigger the MCP tool `search_custom` with specific query terms to inspect the raw Searchspring API response and verify if redirects or custom parameters are triggering.

Run a direct prompt asking Claude Code to look up a specific SKU. It calls `search_sku` and outputs the Searchspring product's price, stock status, and attributes in your terminal.

Yes. Since the MCP server runs in your terminal, you can direct its output into standard tools like jq or grep to parse the Searchspring catalog data further.

It only transmits Searchspring catalog search parameters, category names, and SKU identifiers. No customer records, order histories, or backend admin credentials are ever touched or sent over the network.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript