Wishfinity +w

What is Wishfinity +w?

Wishfinity +w is a universal wishlist infrastructure for AI shopping experiences. It adds "save for later" functionality to any AI assistant, allowing users to save any product URL from any online store by saying "save that."

How to use Wishfinity +w?

Configure the MCP server in Claude Desktop or other MCP clients using the JSON config with npx -y wishfinity-mcp-plusw for local use, or connect to the remote HTTP endpoint at https://wishfinity-mcp-plusw.wishfinity.workers.dev/mcp. The server provides prompts such as save_for_later, shopping_assistant, and gift_ideas, along with resources like an integration guide and trigger phrases.

Key features of Wishfinity +w

• Universal compatibility with any product URL and store
• MCP prompts: save_for_later, shopping_assistant, gift_ideas
• MCP resources: integration guide and trigger phrases
• Dual transport support: stdio (local) and HTTP (remote)

Use cases of Wishfinity +w

• Saving products discovered while chatting with an AI assistant
• Collecting items during browsing and research sessions
• Building a universal wishlist across multiple online stores

FAQ from Wishfinity +w

What makes Wishfinity +w different from browser bookmarks?

Wishfinity +w is a universal wishlist built specifically for AI assistants, allowing users to save any product URL from any store with a simple voice or text command, without needing to manually copy links.

What dependencies are required to run Wishfinity +w locally?

The local transport uses npx (Node.js) to run the package wishfinity-mcp-plusw. Node.js must be installed on your system.

Where are saved wishlist items stored?

The README does not specify data storage details; it only describes the server's capabilities for saving product URLs.

What transport options does Wishfinity +w support?

Wishfinity +w supports both stdio (for local use with MCP clients like Claude Desktop) and HTTP (for remote access via the provided endpoint).

Does Wishfinity +w require authentication or API keys?

The README does not mention any authentication or API key requirements.