All servers / Developer / O3R MCP server
O3R MCP server
Experimental package — This module provides a MCP Server
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 15.3.2. Package: @o3r/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (21.1 seconds including download)
- Tools offered: 4
- Last published: 2026-11-13
- Weekly downloads (npm): 1,403
- License: BSD-3-Clause · Direct dependencies: 9
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
migrate_otter_version2 of 2 parameters describedUse this tool to help users migrate their Otter project to a newer version. **Workflow:** 1. Call this tool to get the current Otter version from the user's `package.json` 2. If no target version is specified, call `get_supported_releases_amadeusitgroup/otter` to fetch available releases 3. Compare the current version with available releases to identify newer versions 4. Present the newer versions to the user and ask which one they want to migrate to 5. Call this tool again with the target version to get migration instructions
angular_schematics1 of 1 parameter describedList Angular schematics (ng generate) and their basic options.
get_best_practicesno parametersA comprehensive guide detailing Otter's best practices for code generation and development. This guide should be used as a reference by an LLM to ensure any generated code adheres to modern Otter and Angular standards.
create_monorepo_with_app2 of 2 parameters describedYou **MUST** use this tool to create a monorepo with an application inside. It is mandatory to follow this guide to ensure all code adheres to Otter standards. This is the first step for any Otter repository.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.