Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @ama-styling/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
claude mcp add ama-styling-mcp -- npx -y @ama-styling/mcp@15.3.2In einem Terminal ausführen.
{ "mcpServers": { "ama-styling-mcp": { "command": "npx", "args": [ "-y", "@ama-styling/[email protected]" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenThe Otter project is a highly modular framework whose goal is to provide a common platform to accelerate and facilitate the development on Angular web applications. It is split into several units to cover different aspects of these applications (localization, testing, customization, etc.). Also, to customize an application, metadata can be extracted from the application source code and injected into a CMS to manage dynamic configuration.
[!TIP] The full list of modules and their documentation is available in the /docs folder. An overview of the technical module interactions and the architecture of the dependencies is available in the architecture section.
A demonstration of a list of features provided by Otter is accessible on the showcase application.
To set up a new Otter project with a monorepo structure, use the following simple command:
# Creating a new Otter monorepo
npm create @o3r my-project
[!TIP] Please refer to Otter Get Started and Angular Get Started for complete documentation.
Please read the Contributing file for details on our code of conduct and the process to submit pull requests.
This repository includes an AGENTS.md file that provides context for AI coding assistants (Claude Code, GitHub Copilot, Cursor, Windsurf, etc.).
The documentation is split into focused context files in .agents/ to optimize token usage - AI agents load only what they need for their current task (testing, building, committing, etc.), reducing token consumption by 50-60% compared to a single large file.
Please refer to Security file.
Please refer to the License file.
The Otter Team, @AmadeusITGroup/otter_admins, is responsible for the review of the code of this repository. Any bug of feature request can be addressed via issue report.
In this monorepo, certain APIs across all packages are marked with the @experimental tag in their TypeScript documentation (TSDoc). This tag highlights that these exports — whether classes, functions, types, or constants — are experimental and may change without warning.
@experimental APIs from any package in this monorepo, pin the package versions explicitly to avoid unexpected breaking changes.These documents describe how to set up your development environment to build and test the framework.
It also explains the basic mechanics of using git, node, and npm.
Refer to the contribution guidelines if you'd like to contribute to the framework.
Before you can build and test Otter modules, you must install and configure the following products on your development machine:
Git and/or the GitHub app (for Mac or Windows)
Node.js, (version >=22.22.3)
engine property of its package.json file.Yarn, a Node's Package Manager
Clone the Otter repository using the button Code or using the following git command:
git clone https://github.com/AmadeusITGroup/otter.git
Next, install the JavaScript modules needed to build:
# Install library project dependencies (package.json)
yarn install
To build the modules, run:
yarn run build
Each module can be built independently thanks to Nx commands:
# ex: Build Core package only
yarn nx build core
[!NOTE] Results are put in the
distof each module (packages/@<scope>/<module>/dist).
Check the formatting:
yarn run lint
Check Unit Tests:
yarn run test
Check Integration Tests:
yarn run test-int
Verdaccio is used to run the integration tests as close as possible to a real npm publication.
Each module can be tested independently thanks to Nx commands:
# ex: Test Core package only
yarn nx test core
# ex: Lint Core package only
yarn nx lint core
When running the Build, Lint, or Test commands, Nx can use its cache mechanism. In some cases, it may be useful to clear the cache to investigate an issue. This can be done with the following command:
yarn nx reset
The repository contains the mandatory configuration and the recommended VSCode plugins to ensure optimal comfort and productivity while developing on the Otter Framework.
The default configuration of the repository provides a way to run Unit Tests one by one and to define, within VSCode, break points using the vscode-jest-tests debugger task.
For Yarn v1, add the resolutions property in the main package.json. It should be filled with the relative path to the dist of the local packages you want to link. The protocol link: can be used.
NOTE: It will not import the transitive dependencies of the linked packages.
Example:
{
"resolutions": {
"@o3r/localization": "./relative/path/to/otter/packages/@o3r/localization/dist",
"@o3r/core": "link:./relative/path/to/otter/packages/@o3r/core/dist",
}
}
For Yarn v2+, the protocol portal: can also be used.
NOTE: The portal protocol will also import all the transitive dependencies of the linked packages. Please keep in mind that mismatched versions of these dependencies may cause some issues.
Example:
{
"resolutions": {
"@o3r/localization": "./relative/path/to/otter/library/@o3r/localization/dist",
"@o3r/core": "link:./relative/path/to/otter/library/@o3r/core/dist",
"@o3r/rules-engine": "portal:./relative/path/to/otter/library/@o3r/rules-engine/dist",
}
}
Due to proxy redirection you may face an SSL certificate issue on Yarn when installing the Otter project locally:
Request Error: self-signed certificate in certificate chain
To solve this, you can provide your own certificate in two different ways:
Experimental package -- MCP module to expose design token information to AI assistants
{ "mcpServers": { "ama-styling-mcp": { "command": "npx", "args": [ "-y", "@ama-styling/[email protected]" ] } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
@ama Styling/mcp läuft lokal über stdio.
Zuletzt geprüft: 2026-11-15. Experimental package -- MCP module to expose design token information to AI assistants