"Magasins U" matching MCP servers:

MCP server for see-u-ui component library, allowing AI assistants to query component props/events/slots/examples on demand.

A custom MCP protocol service that enhances AI models by providing multilingual translation capabilities and resource management, allowing for automatic text extraction and translation through external APIs.

前端ai主导的全流程，自动化的预开发；旨在解决前端开发在联调前期的各种繁琐工作

一个基于Model Context Protocol的SQLite数据库查询服务，为AI应用提供标准化的数据库访问、安全的SQL查询执行以及表结构预览功能。

Enables MCP clients to securely query databases, list tables, inspect table schemas, and test connections across Oracle, SQL Server, MySQL, PostgreSQL, and SQLite using read-only SQL tools.

🎨 AI-powered UI/UX design intelligence - 1519+ curated design resources through MCP | React, Vue, Next.js, Flutter & more

Serial and GDB/SWD MCP servers for real hardware: agents read consoles, drive U-Boot, set breakpoints, and probe unknown Cortex-M boards.

An MCP server that enables local AI models to receive guidance from remote 'senior' AI providers like OpenAI, Anthropic, and Gemini to solve programming problems. It features intelligent multi-turn dialogue management, context synchronization, and automated session history tracking.

An MCP server for Arabic UI/UX design, offering tools to generate design tokens, build RTL components, stitch layouts, and audit RTL compliance using Material 3 Expressive and Google Stitch.

Enables comprehensive UI/UX development workflows through integrated tools for component development with Storybook, Tailwind CSS styling, Framer Motion/GSAP animations, Playwright testing, and automated design system generation. Provides end-to-end automation for visual regression testing, accessibility compliance, and UX optimization analysis.

MCP server for 友盟 U-App mobile analytics, enabling AI agents to query app statistics, retention, channels, versions, custom events, and more via the OpenAPI.

远程MCP服务，通过Model Context Protocol为AI应用提供阿里云数万个OpenAPI的无缝集成，支持Terraform、多账号、自定义OAuth等能力。

Official MCP Server for GPT-5.6 Sol Coding & Reasoning API. Connects extended reasoning capabilities directly into Claude Desktop, Cursor, and Windsurf.

A secure and scalable Git MCP server giving AI agents powerful version control for local and (soon) serverless environments.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables compatible MCP AI tools to read, write, design windows, and run programs in the E-Language IDE.

Enables MCP/AI clients to read project state and execute protected PCB operations in EasyEDA Pro via a local Bridge and official extension APIs.

Connects a DeepSeek Harness agent to 嘉立创EDA专业版 / EasyEDA Pro through a local loopback bridge and JLCEDA extension, letting it search and place components, draw wires, net flags and labels, inspect and delete primitives, and save or zoom schematic documents. It also covers PCB work: placement and movement of components, tracks, vias, regions and board outlines, auto-place and auto-route with job polling, DRC, copper pours, and Gerber export.

Je dois répondre en JSON avec name et description. Name = "jevmem" (le nom du serveur MCP publié). Description : décrit ce que le serveur permet, sans répéter le nom. Par exemple : "Saves decisions, rules, bugs, to-dos and dead ends from Claude Code and Cursor chats into a versioned JEVMEM.md file in the repository, then brings the relevant lines back in later sessions and checks tool calls against saved rules before they run." Je dois vérifier : ne pas citer de personne/mainteneur/organisation. Ne pas répéter le nom. Deux phrases max. Éviter de mentionner "jevmem" comme nom. Je peux dire "Saves..." sans nom. Ça mentionne JEVMEM.md, ce n'est pas le nom du serveur mais le fichier, c'est autorisé ? La consigne : la description ne doit pas reprendre le nom. Le nom est "jevmem" ; "JEVMEM.md" contient jevmem. Mieux éviter. Je vais dire "a markdown memory file in the repository". Éviter aussi les noms d'organisations (TypeSafe, Anthropic, Claude Code...). Claude Code est un produit, pas une personne/organisation. Mais prudence : ne pas citer de mainteneur ou d'organisation. Je peux dire "coding-agent chats". La description doit dire ce que le serveur permet. Je vais faire deux phrases.

An MCP server that enables GitHub API operations such as managing repositories, issues, and pull requests through natural language.