Rosetta MCP server
Commit Nov 13, 2026Loads shared engineering instructions, architecture, standards, and guardrails into AI coding sessions via MCP.
Also known as griddynamics/rosetta
- Stars
- 375
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 13, 2026
- License
- Apache-2.0
What is Rosetta MCP?
Rosetta loads shared engineering instructions, architecture, standards, and guardrails into AI coding sessions via MCP.
Summary generated from the project's README
About Rosetta MCP server
Providing engineering governance and context for AI coding agents is what Rosetta enables for development teams. It integrates shared architecture, standards, and guardrails directly into AI coding sessions to prevent agents from making incorrect assumptions about your specific codebase. By encoding your team's engineering discipline, it ensures that tools like Claude Code, Cursor, Copilot, and Codex follow established workflows rather than guessing from a few open files.
This open-source solution runs within your perimeter and uses Git for versioning all instructions. It functions through a series of reusable skills that can be called by name or managed automatically by the rosetta skill. Users can implement a structured process following five distinct phases: Prepare, Research, Plan, Act, and Validate. The system is designed to work with existing MCP-compatible agents, allowing teams to maintain consistency across different IDEs and AI models without relying on proprietary agents.
What you can do with it
- 1Establishing project contextProvide an AI agent with your business logic and architectural history before it begins any coding tasks.
- 2Automating technical requirementsGenerate precise requirement units including acceptance criteria and dependencies to build into user stories.
- 3Performing security reviewsConduct threat modeling and review code, containers, and cloud configurations to produce remediation tasks.
- 4Managing large repositoriesSplit massive codebases into non-overlapping scopes for multiple subagents to handle simultaneously.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablegriddynamics/rosetta is public and reachablegithub.com/griddynamics/rosetta ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/griddynamics/rosetta ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubWhat is Rosetta
https://github.com/user-attachments/assets/6df6e217-3e5c-4691-84ed-7440701a87de
AI coding agents are great — until you try to use them across a real team. Everyone builds their own prompts and instructions, knowledge stays in silos, and the agent — not knowing your architecture or constraints — guesses from a few open files and confidently does the wrong thing.
That's why we built Rosetta — open-source engineering governance and context for AI coding agents. It's not another proprietary agent; it works with the tools you already use (Claude Code, Cursor, Copilot, Codex, and other MCP-compatible agents) and loads your team's shared engineering instructions into every session. Everything is versioned in Git and can run inside your perimeter.
Teach agents how to think, not what to do. The model already knows Python and React; what it lacks is your engineering discipline. That's what Rosetta encodes.
[!NOTE] If you are effectively using your current setup, writing your own skills, and managing AI using your own processes, you probably don't need Rosetta.
User Guide
Rosetta-guided work follows five phases — Prepare → Research → Plan → Act → Validate — with approval gates at the key decision points.
Read more in the User Guide.
Quick Start
Overall Process: Install (plugin preferred) → Initialize workspace → Configure workspace ecosystem (tools, MCPs) → Proceed with Coding, Modernization, Analysis, etc.
Please follow Quick Start Guide which will walk you through the process.
Very detailed information on installation and configuration in all available modes is in Installation Guide.
Skills
Reusable units of work the AI loads on demand. If your tasks are small to medium use skills. Workflows pick them for you, and most can also be called by name.
Let Rosetta decide
rosetta: You want Rosetta to handle it itself. Classifies your request, picks the matching workflow, and runs it end to end.
Understand what exists
load-project-context: Gives the AI your project's business context, architecture, and past decisions before any work starts.codemap: Gives the AI a structural map of the repo to navigate by. Uses your LSP or code-graph tooling when available.discovery: Evidence-backed picture of what exists today, including whether this was already attempted and done wrong.reverse-engineering: Recovers domain rules and intent from code into business specs.research: Researches any question grounded in your project, with real sources. Compares options and validates its own conclusions.
Decide what to build
requirements-authoring: Precise and atomic requirement units: EARS acceptance criteria, rationale, alternatives, dependencies, traceability. You combine them into stories or features.requirements-use: Plans and builds from approved requirements. Every task, test, and result traces back to a requirement ID.design: Deep architecture decisions with defended rejections, plus domain playbooks: distributed systems, multi-tenancy, payments, regulated data, migrations.tech-specs: Produces target-state interfaces, API contracts, data models, and security considerations. Forces the AI to read the real code, grounding its assumptions.planning: An ordered graph of AI sessions for automated execution, each with its own scope, checklist, and handoff.backlog: Turns a thin ticket into a buildable one: gaps found, questions posed, facts written back. Also produces a WBS for people.reasoning: Breaks a hard problem down, identifies roles, boundaries, events, models. Works via Tree-of-Thoughts, expanding every alternative to its conclusion before committing.
Build it
coding: Simple, minimal, in-scope changes following KISS/SOLID/DRY. Systematic dependency-ordered validation: database, API, web, mobile. Covers IaC.testing: Isolated and idempotent at 80%+ coverage, external calls mocked only. Scenario tests start from a sequence diagram: what depends on what, what is shared setup, then the test.debugging: OODA. Root cause with evidence before any fix, one hypothesis at a time, prevention recommended. Three failed fixes means a design problem.security: Threat modeling plus code, dependency, IaC, container, cloud, and API review. Secrets gated before ingestion, active testing only where authorized. Output is remediation tasks.natural-writing: Strips AI giveaways: hype words, em-dashes, rhetorical questions, fake engagement. For docs, emails, posts, release notes.
Test automation and QA
qa-knowledge: QA engineering end to end: sources into requirements, gap analysis, Given-When-Then specs, TMS export, runnable API and UI tests, failure triage. Every case is implemented or recorded as a gap, never dropped.qa-structure: Canonical paths, slugs, and state files for QA runs. Each session in its own folder, so parallel runs never collide and a long flow knows which phase is done.data-collection: Read-only pull from issue tracker, test management, wiki, and the codebase. A ticket gets recorded, not acted on. Gaps and permission walls recorded, never guessed.
Delegate the work
orchestration: Sizes the work, builds and briefs a subagent team, and gates every result through fresh eyes instead of self-review. Large plans run with phases, steps, and tasks.subagent-directives: Requested automatically by the orchestrator for every subagent: stay in scope, stop and report when blocked rather than improvise, prove each claim with links and line ranges.large-workspace-handling: Use when a repository is too big to handle at once. Splits into non-overlapping scopes, one subagent each, then a second wave verifies the work.coding-agents-farm: Runs Claude, Codex, Copilot, Gemini and others in parallel on isolated git worktrees, for throughput or cross-model validation. Burns money fast, so it is gated behind explicit consent.
Keep the session on track
hitl: Makes the AI work together with you. Approval gates at specs, implementation, and closing, with review in small batches. A clear affirmative counts.questioning: A few high-impact questions before work starts, each one decision, with why it matters and a recommended answer. Anything researchable it answers itself.self-organization: Keeps work organized as it grows: splits oversized tasks and files, clears stale content, flags when a session should restart. Announces before it reorganizes.
Stay safe
sensitive-data: Secrets, keys, PII, PHI, and payment data never get read, printed, logged, or committed. Masked on sight, and the same care applies to the code it writes.dangerous-actions: Before anything irreversible: blast radius first, safer alternatives offered, explicit approval required. Higher environments are off limits.risk-assessment: Checks what the AI can actually reach, such as databases, cloud accounts, and production servers. Rates the risk and blocks outright when it is critical.
Recover when it goes wrong
deviation: Stops the moment work no longer matches what you asked, or the AI cannot stand behind its own solution. Escalates instead of pressing on.self-learning: After a failure or a wrong result, stops and finds the cause, then records a reusable rule in the repo's memory so it does not repeat.post-mortem: Diagnoses why a session went wrong across your prompt, workspace docs, local config, Rosetta instructions, and tooling. Can file a sanitized issue when Rosetta is at fault.
Extend
harness: Builds what the AI needs to run and check your system: command-line and MCP actions, dev containers, skills, subagents, workflows, hooks, and unattended automation. Encoded once, proved on every run.coding-agents-prompt-authoring: Write, review, harden, and port your own skills, subagents, workflows, and rules, including between different IDEs and agents.coding-agents-hooks-authoring: Author, register, and debug hooks that fire on agent actions across every supported IDE.
Domain packs
solr-query: Apache Solr queries that return what you meant: eDisMax, block join, JSON facets, kNN, explain output, relevancy tuning.solr-schema: Apache Solr schema and solrconfig, audit or design: field types, analyzer symmetry, docValues, synonyms, commit strategy.solr-extending: Custom Apache Solr plugins: SearchComponent, DocTransformer, QParser, update processors, function queries, and their solrconfig wiring.solr-semantic-search: Phrase-tagging semantic search on Solr: concept tagging, taxonomy, graph paths, ambiguity resolution. Lexical, not vector.specflow-use: Connects your workspace to Grid Dynamics SpecFlow through its MCP.
Top Workflows
Workflows are more expensive to run, those are supposed to be used on large areas of work: entire feature or multiple related features at once. It is expected to give tasks that those workflows will work on for hours.
coding-flow: AI creates features, fixes defects, and performs refactoring, everything end-to-end. AI performs discovery, design, specs and a plan, user review, then AI implements and runs separate review and validation passes (including running application). Most useful for medium to large coding tasks, and for controlled component-by-component migration/modernization work.requirements-authoring-flow: AI works with user and raw artifacts to define entire-application requirements. AI discovers context and existing constraints, captures intent, drafts atomic requirement units, validates them, and finalizes traceability artifacts. This is the most efficient use of coding agents. Requirements then Coding.security-flow: AI runs an authorized, evidence-preserving security review through mandatory specialist subagents. It gates secret-bearing files before source ingestion, bounds active testing to approved pre-production targets, independently reviews evidence, and prepares concise inputs for a later coding flow without starting remediation.testgen-flow,api-aqa-flow,ui-aqa-flow: AI handles QA-related work such as generating test cases and creating API or UI automation tests. AI first collects project context, requirements, and existing QA assets, clarifies gaps, and only after that generates test cases or automation tests.code-analysis-flow: AI creates grounded analysis documents based on the codebase. AI first loads project context, asks clarification questions, then produces either one focused analysis document or parallel module analyses plus a summary.help-flow: AI explains available Rosetta workflows, skills, and agents. Most useful when the user is unsure which Rosetta capability to use.init-workspace-flow: AI sets up a repository for AI use in both brownfield and greenfield projects. AI first analyzes the workspace, builds baseline docs, asks gap-filling questions, and verifies the result. Use it once per repository as its purpose is to build context for subsequent sessions.
If you prefer to follow your own workflows, check the skills above.
Without Rosetta / With Rosetta
| Without Rosetta | With Rosetta |
|---|---|
| Each developer writes their own prompts and instructions | One versioned, shared source of truth |
| The agent guesses from a few open files | It reads your architecture and conventions first |
| Starts coding immediately | Prepare → research → plan → act → validate |
| Reviews its own work in the same context | A fresh-context reviewer subagent checks it |
| "Generate and hope" | Validation with real execution evidence |
| Knowledge stuck in senior engineers' heads | Captured once, reused everywhere |
Example: "Add rate limiting to the checkout API"
| Without Rosetta | With Rosetta |
|---|---|
| Jumps straight into editing the handler | Reads ARCHITECTURE.md and your existing conventions first |
| Misses the shared middleware pattern; duplicates the Redis client | Reuses the shared rate-limiter and Redis layer |
| No plan, no checkpoint | Proposes a plan and asks for approval |
| Ships without running tests | Runs the integration tests, then a fresh-context reviewer validates |
How it works
Rosetta layers your instructions at runtime — core, then organization, then project, each building on the one above — and adapts the result to whatever agent you use:
flowchart LR
A["<b>Core</b><br/>best practices & workflows"] --> B["<b>Organization</b><br/>standards, policies & guardrails"]
B --> C["<b>Project</b><br/>architecture, context & constraints"]
C --> R["<b>Rosetta Runtime</b><br/>context engineering + instruction orchestration"]
R --> AD["<b>Agent Adapters</b>"]
AD --> G["<b>Guided Execution</b><br/>workflows • guardrails • validation"]
G --> T["Claude Code · Cursor · Copilot · Codex · Antigravity"]
classDef rosetta fill:#1f6feb,stroke:#1b4fb8,color:#ffffff;
classDef yours fill:#2da44e,stroke:#1a7f37,color:#ffffff;
classDef third fill:#d0d7de,stroke:#8c959f,color:#1f2328;
class A,R,AD,G rosetta
class B,C yours
class T third
Legend: 🟦 shipped with Rosetta (Core, Runtime, adapters, execution) · 🟩 authored by your org & project · ⬜ your existing AI tools (third-party).
Higher layers propagate to every project automatically; teams customize without forking. Everything is authored in markdown and versioned in Git.
Tech Demo: Init and Coding
https://github.com/user-attachments/assets/fc0ef06a-2f9c-49fa-bc05-68001dadd286
Tech Demo: Frontend Migration
https://github.com/user-attachments/assets/8a48ce2e-a8f6-4d80-a208-4e808ab502df
Why not just use IDE rules?
IDE rules (.cursorrules, CLAUDE.md, Copilot custom instructions) are useful, but they are usually local to one tool, one repo, or one developer. Rosetta makes instructions layered, versioned, reusable, and portable across agents and IDEs — organization standards flow into every project, while project-specific context stays local and customizable. On top of that, Rosetta adds the workflows, guardrails, and approval gates that flat rules files do not provide.
Why use it
| For builders | For organizations |
|---|---|
| Deep project context — reads your architecture and conventions, not a few open files | One standard across every team, tool, model, and repo |
| Plain-language tasks — a slash command, no prompt scaffolding or new syntax | No vendor lock-in — one instruction set across Claude Code, Cursor, Copilot, Codex; engineers keep their IDEs |
| Ready-made flows — coding, testing, AQA, research, and more | Versioned control — review, approve, and roll back instructions in Git |
| Plans and approval gates before code, not after the damage | Knowledge captured once — out of senior engineers' heads |
| Fresh-context review and execution-backed validation | Cross-repository intelligence — agents see the system, not just one repo |
| Less babysitting — fewer wrong turns to catch and re-prompt | Runs inside your perimeter — works with limited internet access; no source code leaves |
Rosetta MCP questions
What is Rosetta?
Rosetta is an open-source engineering governance layer that provides shared instructions, architecture, standards, and guardrails to AI coding agents in every session.
Which AI tools does Rosetta work with?
Rosetta works with Claude Code, Cursor, Copilot, Codex, and other MCP-compatible agents.
How does Rosetta guide the AI's work?
Rosetta follows a five-phase process: Prepare, Research, Plan, Act, Validate, with approval gates at key decision points.
How is Rosetta versioned and deployed?
All Rosetta content is versioned in Git and can run inside your own perimeter.