Serveur MCP each::labs
Commit 29 oct. 2026Générez et éditez des images, des vidéos, de la musique et de la voix en utilisant des modèles d'IA et des workflows organisationnels via des interfaces conversationnelles.
Aussi connu sous eachlabs/plugin, plugin
- Étoiles
- 0
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 0.3.0
- Dernier commit
- 29 oct. 2026
- Licence
- MIT
Qu'est-ce que each::labs MCP ?
each::labs est un serveur MCP. Générez et éditez des images, des vidéos, de la musique et de la voix en utilisant des modèles d'IA et des workflows organisationnels via des interfaces conversationnelles.
Résumé généré à partir du README du projet
À propos du MCP server each::labs
each::labs permet aux développeurs et aux équipes créatives de créer et de modifier des ressources multimédias via des interfaces conversationnelles. Vous pouvez générer ou éditer des images, des vidéos, de la musique et de la voix en utilisant des modèles d'IA directement au sein de vos environnements de chat. Le serveur gère également des tâches de traitement de médias telles que le découpage, le recadrage, le redimensionnement et la conversion de fichiers, comme l'extraction d'audio à partir d'une vidéo ou la transformation d'un clip en GIF.
Cet outil s'intègre à Claude Chat, Claude Desktop, Claude Code, Codex CLI, Codex app et Grok Build. Au lieu de gérer des clés API complexes, il vous suffit de vous connecter avec votre compte each::labs existant pour établir la connexion. Pour les organisations, un propriétaire peut fournir une adresse de connecteur spécifique pour permettre à tous les membres d'exécuter des workflows facturés au compte de l'entreprise plutôt qu'aux comptes personnels.
Des cartes interactives apparaissent dans le chat pour vous aider à gérer le processus créatif. Ces cartes vous permettent de télécharger des fichiers jusqu'à 100 MB, d'ajuster les paramètres des modèles via des formulaires, de choisir parmi plusieurs variantes générées et de comparer les médias édités à l'aide d'un curseur avant/après. Tandis que les applications de chat affichent ces cartes visuelles, les outils en ligne de commande comme Claude Code et Codex CLI fournissent les mêmes résultats sous forme de texte.
Ce que vous pouvez faire avec
- 1Générer et sélectionner des variantes d'imagesDemandez à l'IA de créer plusieurs versions d'un concept visuel spécifique et choisissez votre préférée pour poursuivre la conversation.
- 2Automatiser les workflows médias de l'organisationDéclenchez des processus de production complexes et multi-étapes que votre entreprise a déjà définis dans le tableau de bord.
- 3Effectuer un montage vidéo et audio rapideDonnez instruction à l'assistant pour couper des durées spécifiques d'une vidéo ou modifier son format pour les réseaux sociaux.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer each::labs MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller each::labs MCP dans Claude Code
$ claude mcp add --transport http plugin https://mcp.eachlabs.ai/mcpInstaller each::labs MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"plugin": {
"url": "https://mcp.eachlabs.ai/mcp"
}
}
}Installer each::labs MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"plugin": {
"type": "http",
"url": "https://mcp.eachlabs.ai/mcp"
}
}
}Installer each::labs MCP dans VS Code CLI
$ code --add-mcp '{"name":"plugin","type":"http","url":"https://mcp.eachlabs.ai/mcp"}'Installer each::labs MCP dans Codex
$ codex mcp add plugin --url https://mcp.eachlabs.ai/mcpInstaller each::labs MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.plugin] url = "https://mcp.eachlabs.ai/mcp"
Installer each::labs MCP dans Gemini CLI
$ gemini mcp add -s user --transport http plugin https://mcp.eachlabs.ai/mcpInstaller each::labs MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"plugin": {
"url": "https://mcp.eachlabs.ai/mcp",
"type": "http"
}
}
}Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessibleeachlabs/plugin is public and reachablegithub.com/eachlabs/plugin ↗Réussi
- Le nom du package correspond au dépôt sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-10-29github.com/eachlabs/plugin ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPHTTPS endpoint answered 401 (sign-in required)Réussi
README
Voir sur GitHubeach::labs plugin for Claude, Codex and Grok Build
Generate and edit images, video, music and voice with each::labs models, and run your organization's each::labs workflows, by asking in a conversation. The plugin also cuts, crops, resizes and converts media, and shows small interactive cards inside the chat where you upload a file, adjust a model's settings or pick one of several results.
It works in Claude Chat (claude.ai), Claude Desktop, Cowork and Claude Code, and in the Codex app, Codex CLI and Grok Build. You sign in with your each::labs account; there is no API key to paste.
Install
The plugin is installed from its own marketplace, eachlabs/plugin.
The same repository serves Claude, Codex and Grok Build.
| Where | How |
|---|---|
| Claude Chat, Claude Desktop | Customize, Plugins, Add marketplace, enter eachlabs/plugin, then add the eachlabs plugin |
| Claude Code | claude plugin marketplace add eachlabs/plugin, then claude plugin install eachlabs@eachlabs |
| Codex CLI | codex plugin marketplace add eachlabs/plugin, then codex plugin add eachlabs@eachlabs, then codex mcp login eachlabs |
| Codex app | Add the marketplace with the CLI command above, then install the eachlabs plugin from Plugins |
| Grok Build | grok plugin install eachlabs/plugin --trust, then sign in when Grok opens the each::labs page in your browser |
Team and Enterprise. An Owner can add the connector
https://mcp.eachlabs.ai/mcp for the whole organization. Each member adds the
plugin marketplace themselves, because organization-wide plugin sync on
claude.ai accepts only the organization's own private repositories. Each member
then signs in with their own each::labs account. That account must belong to
the each::labs organization that should pay for the runs; a member who signs in
with a personal account is billed there instead.
Updating. In Claude Chat and Claude Desktop a plugin installed from the
marketplace updates automatically, with no restart. In Claude Code, run
claude plugin update eachlabs@eachlabs, then /reload-plugins. In Codex, run
codex plugin marketplace upgrade. In Grok Build, run grok plugin update eachlabs.
Sign in
After installing, open the plugin's Connectors tab and choose Connect. A browser window opens on each::labs: sign in and pick the organization to use. Every model run and workflow run is billed to that organization, the same way as a run from the each::labs dashboard or API.
In Grok Build, the browser opens the first time the plugin is used. To sign in
again, open /mcps and press i on eachlabs.
What to ask
Ask in your own words. Claude chooses the model, reads its inputs and runs it. Some examples:
| Task | Example |
|---|---|
| Images | "Generate a product photo of a white sneaker on a marble table, soft studio light." |
| Images | "Give me 4 variants of a fantasy trading card with a fire dragon, I want to pick one." |
| Image editing | "Remove the background from this photo." "Turn this portrait into a watercolor painting." |
| Video | "Turn this image into a 5-second clip where the camera slowly pushes in." |
| Video | "Make a 10-second video of waves hitting a lighthouse at sunset." |
| Music | "Compose a 30-second upbeat lo-fi beat for an intro." |
| Voice | "Read this paragraph aloud in a calm male voice." "Transcribe this interview." |
| Cutting and cropping | "Cut the first 10 seconds of this video." "Crop this video to 9:16 for a story." |
| Converting | "Convert this clip to a GIF." "Extract the audio from this video as mp3." |
| Workflows | "Which workflows do we have?" "Run our product clip workflow with this photo." |
When a task has several steps, such as restyling a photo and then animating it, Claude first looks for one of your organization's workflows that does the whole job, and runs it if one fits.
Cards in the conversation
In the chat apps, Claude Chat (claude.ai), Claude Desktop and the Codex app, some answers come with a small card instead of plain text. Terminals such as Claude Code, Codex CLI and Grok Build show the same results as text.
| You see | When |
|---|---|
| A file picker with "Choose a photo" and a progress bar | A model needs a file you have not linked. One card takes a whole set of files, for example all the screenshots for a slideshow. The files go from your browser straight to each::labs storage |
| A form with the model's settings and a Run button | You ask to adjust settings, or a run has options worth choosing first |
| The result: the image, a video or audio player, and download buttons | Every run that produces media. A file in several formats has one button per format. A workflow's outputs show together as a gallery |
| Several results to choose from, and a "Use this variant" button | You asked for several variants. Click between them as often as you like, then press "Use this variant"; Claude continues with that one, and the choice is final |
| A Compare button under an edited image or video | The result is an edit of a file you gave. Drag the handle to compare before and after |
| A timeline with two handles, or a rectangle on the first frame | You want to cut a clip or crop a frame and have not given exact numbers |
| A workflow's inputs as a form, with a file picker for each photo, video or audio input | A workflow needs inputs you have not given |
After you press a card's button, Claude continues on its own. You do not need to type anything. A card you already used stays locked on your choice when you come back to the conversation later.
After the first run of a model in a conversation, Claude ends its reply with a short Adjust generation settings line naming a few of that model's settings. Ask to change any of them and the settings form appears.
Limits
- each::sense skills are not included. The public eachlabs/skills collection also has skills that run through each::sense, the each::labs agent. Access to each::sense is restricted to specific organizations, so this plugin does not include those skills. Most of their tasks, such as background removal, upscaling, trimming or watermarking, work through the models and video tools above.
- Files live on each::labs storage. Uploads and results are stored by each::labs and shown from there. Anyone who has a file's link can open it; the links are long random addresses, not listed anywhere. Files are kept for 180 days, or for your organization's own retention period if it set one, and can be deleted earlier from the storage page in the each::labs dashboard.
- Uploads. One upload card takes up to 50 files, or fewer when the chosen model accepts fewer, and up to 100 MB per file. Files upload four at a time. A card refuses too many files or a file that is too large before anything uploads. The same limits apply to the file fields on a workflow's form.
- Long jobs. A video can take a few minutes. Claude waits for it; if a run takes longer than the wait, Claude checks again until it finishes.
- Variants. Up to 8 results of one prompt in a single request, unless the model itself can make more in one run.
- Workflows. Claude can list, read and run your organization's workflows and show their results. Building or editing a workflow is done in the each::labs dashboard.
- Phones. Cards work in the Claude app; the file picker opens your photo library, not the camera.
- Trimming FLAC audio returns an mp4 file, because the trim copies the audio without converting it. mp3, wav and m4a keep their format.
Troubleshooting
| Problem | What to do |
|---|---|
| A new card or an update does not show | Start a new conversation. If it still does not show, reload claude.ai or restart Claude Desktop |
| A card says it takes fewer files than you have | Tell Claude how many files you have, or ask for another card for the rest |
| Tools fail with a sign-in or permission error | Open the plugin's Connectors tab, disconnect, and connect again |
| A card does not appear, only text | Check you are in Claude Chat or Claude Desktop; Claude Code shows text only. Ask Claude to show the result again |
| A card says a file is no longer available | Ask Claude to show the file again; it fetches a fresh copy of the result |
| The wrong organization is billed | Disconnect the connector and sign in again, picking the right organization |
Data
The plugin connects to one address, https://mcp.eachlabs.ai/mcp, and needs
only an each::labs sign-in: no API key, and no scripts or hooks run on your
machine.
Your prompts and input file links go to the each::labs MCP server, which runs them on the each::labs API under the organization you picked at sign-in. A file you add on a card goes from your browser to each::labs storage and does not pass through Claude. The plugin stores nothing itself.
Contributing
How the repository is laid out, how the skills are generated and how a version is released is in CONTRIBUTING.md.
Questions sur each::labs MCP
Comment ajouter each::labs MCP à Claude Code ?
Exécutez claude mcp add --transport http plugin https://mcp.eachlabs.ai/mcp dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter each::labs MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Comment puis-je me connecter au plugin ?
Vous vous connectez à l'aide de votre compte each::labs via une fenêtre de navigateur qui s'ouvre après avoir choisi Connect dans l'onglet Connectors du plugin.
Ai-je besoin d'une clé API pour utiliser each::labs ?
Non, le plugin utilise la connexion à votre compte each::labs au lieu d'une clé API.
Où sont stockés mes fichiers téléchargés et les médias générés ?
Les fichiers sont stockés sur le stockage each::labs, et non sur votre machine locale ou dans Claude.
Puis-je exécuter des workflows organisationnels personnalisés ?
Oui, Claude peut lister, lire et exécuter des workflows définis par votre organisation dans le tableau de bord each::labs.