FindMine Shopping Stylist offers AI-powered fashion recommendations, outfit creation, and style guides for e-commerce pl
Add new capabilities to Claude beyond text generation
Example: Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example: Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example: Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Time estimate: 15-60 minutes depending on server complexity
Prerequisites
Mastra Docs
Mastra Docs: AI assistants with direct access to Mastra.ai’s full knowledge base for faster, smarter support and insight
n8n
n8n offers conversational workflow automation, enabling seamless software workflow creation and management without platf
XcodeBuild
XcodeBuild streamlines iOS app development for Apple developers with tools for building, debugging, and deploying iOS an
Linear
MCP server for Linear — enables Claude to interact with Linear data and workflows.
Repomix
Optimize your codebase for AI with Repomix—transform, compress, and secure repos for easier analysis with modern AI tool
We wired FindMine Shopping Stylist into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
FindMine Shopping Stylist has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: FindMine Shopping Stylist surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Strong directory entry: FindMine Shopping Stylist surfaces stars and publisher context so we could sanity-check maintenance before adopting.
FindMine Shopping Stylist reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend FindMine Shopping Stylist for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
According to our notes, FindMine Shopping Stylist benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired FindMine Shopping Stylist into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
I recommend FindMine Shopping Stylist for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
FindMine Shopping Stylist reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 66
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"findmine-mcp": {
"command": "npx",
"args": [
"-y",
"findmine-mcp"
],
"env": {
"FINDMINE_APP_ID": "your_app_id"
}
}
}
}Connects to FindMine's API to provide AI-powered fashion styling recommendations, outfit creation, and product discovery for e-commerce applications.
FindMine Shopping Stylist is an official MCP server published by findmine that provides AI assistants with tools and capabilities via the Model Context Protocol. FindMine Shopping Stylist offers AI-powered fashion recommendations, outfit creation, and style guides for e-commerce pl It is categorized under ai ml, developer tools.
You can install FindMine Shopping Stylist in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
A Model Context Protocol (MCP) server that integrates FindMine's powerful product styling and outfitting recommendations with Claude and other MCP-compatible applications.
This MCP server connects to FindMine's styling API and exposes its functionality to Large Language Models through the Model Context Protocol. It allows users to:
product:/// URI schemelook:/// URI scheme# Install and run directly (recommended)
npx findmine-mcp
# Or install globally
npm install -g findmine-mcp
findmine-mcp
docker run -e FINDMINE_APP_ID=your_app_id findmine/mcp-server:latest
# Clone the repository
git clone https://github.com/findmine/findmine-mcp.git
cd findmine-mcp
# Install dependencies
npm install
# Build the server
npm run build
# For development with auto-rebuild
npm run watch
| Variable | Description | Default |
|---|---|---|
FINDMINE_API_URL | FindMine API base URL | https://api.findmine.com |
FINDMINE_APP_ID | Your FindMine application ID | DEMO_APP_ID |
FINDMINE_API_VERSION | API version to use | v3 |
FINDMINE_DEFAULT_REGION | Default region code | us |
FINDMINE_DEFAULT_LANGUAGE | Default language code | en |
FINDMINE_CACHE_ENABLED | Enable response caching | true |
FINDMINE_CACHE_TTL_MS | Cache time-to-live in ms | 3600000 (1 hour) |
NODE_ENV | Set to "development" for sample data | - |
The server automatically configures Claude Desktop during installation. To verify:
macOS:
cat ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows:
type %APPDATA%\Claude\claude_desktop_config.json
# Build and watch
npm run build # Build the project
npm run watch # Watch for changes and rebuild
npm run typecheck # Run TypeScript type checking
# Testing
npm test # Run tests in watch mode
npm run test:run # Run tests once
npm run test:coverage # Run tests with coverage report
# Code quality
npm run lint # Run ESLint
npm run lint:fix # Run ESLint with auto-fix
npm run format # Format code with Prettier
npm run format:check # Check code formatting
# Development tools
npm run inspector # Run MCP inspector (http://localhost:5173)
This project uses Vitest for testing. Tests are located in __tests__/ directories alongside source files.
# Run tests in watch mode
npm test
# Run tests once (useful for CI)
npm run test:run
# Generate coverage report
npm run test:coverage
Before committing code:
# Run all checks
npm run typecheck && npm run lint && npm run format:check && npm run test:run
The project uses:
Run the server with sample data:
NODE_ENV=development npm run build && node build/index.js
The style guide can be customized to match your brand's specific styling philosophies and fashion guidance. To customize the style guide:
src/content/style-guides.tsgeneral, color_theory, body_types, etc.)styleGuides objectExample of adding a custom style guide category:
// In src/content/style-guides.ts
export const styleGuides: Record<string, string> = {
// Existing categories...
// Add your custom category
your_brand_style: `# Your Brand Style Guide
## Brand Aesthetic
- Key elements of your brand's visual identity
- Core style principles
- Signature looks and combinations
## Your Brand's Styling Do's
- Brand-specific styling recommendations
- Preferred color combinations
- Signature styling techniques
## Your Brand's Styling Don'ts
- Combinations to avoid
- Styling approaches that don't align with brand identity
- Common styling mistakes to avoid
`
};
For complete customization, you can modify the entire get_style_guide handler in src/handlers/tools.ts.
src/
├── index.ts # MCP server bootstrap and initialization
├── config.ts # Environment configuration
├── api/ # FindMine API client
│ └── findmine-client.ts
├── handlers/ # MCP protocol handlers
│ ├── tools.ts # Tool execution handlers
│ ├── resources.ts # Resource handlers
│ └── prompts.ts # Prompt handlers
├── tools/ # Tool definitions with MCP annotations
│ └── index.ts
├── schemas/ # Zod validation schemas
│ ├── tool-inputs.ts # Input validation for all tools
│ └── index.ts
├── content/ # Static content
│ └── style-guides.ts # Style guide content
├── prompts/ # Prompt definitions
│ ├── findmine-help.ts
│ ├── outfit-completion.ts
│ ├── styling-guide.ts
│ └── index.ts
├── services/ # Business logic layer
│ └── findmine-service.ts
├── types/ # TypeScript type definitions
│ ├── findmine-api.ts
│ └── mcp.ts
└── utils/ # Utility functions and helpers
├── cache.ts
├── formatters.ts
├── logger.ts
├── mock-data.ts
└── resource-mapper.ts
This server is built with:
{
"name": "get_style_guide",
"arguments": {
"category": "color_theory",
"occasion": "wedding"
}
}
{
"name": "get_complete_the_look",
"arguments": {
"product_id": "P12345",
"product_color_id": "C789"
}
}
{
"name": "get_visually_similar",
"arguments": {
"product_id": "P12345",
"product_color_id": "C789",
"limit": 5
}
}
# Login to npm
npm login
# Publish the package
npm publish
# Update the version for future releases
npm version patch
# Build the Docker image
docker build -t findmine/mcp-server:latest .
# Login to Docker Hub
docker login
# Push the image
docker push findmine/mcp-server:latest
This project is licensed under the MIT License.
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Notion
MCP server for Notion — enables Claude to interact with Notion data and workflows.