argot MCP server

argot is a helper that looks at code changes and compares them to how your repository has always been written. It notices things like a brand new library nobody on the team uses, a function that already exists somewhere else, or a test that quietly got weaker. It is handy for developers and reviewers who want a second pair of eyes on code that an AI wrote.

What this MCP server does

You ask your AI to review some code changes. Your AI passes that request to argot through this connection. argot compares the changes to patterns it learned from your repository's own git history. It then hands back a list of things worth a closer look, like a foreign dependency or a duplicated function. Your AI shows you those findings so you can decide what to do.

Click to zoom

What you can do with it

• Spot imports of libraries your repository has never used
• Flag new functions that duplicate something you already have
• Point out code that looks like it belongs in a different module
• Warn when a test was deleted, skipped, or made weaker
• Notice when a change reverses the usual direction between layers
• Review a whole set of changes or just one part of it

Try asking your AI

• “Check my latest changes against this repo's history and tell me what looks out of place”
• “Does this pull request add any dependencies we have never used before?”
• “Is there already a function in this repo that does what I just wrote?”
• “Did any tests get weakened or removed in these changes?”

What it gives back to you

You get a list of findings, each with a short label and some evidence from your repository. It might say something like a foreign import was found, or a test was disabled, and point to the file and line. Your AI can then explain them to you in plain words or help you fix them. Nothing in your code is changed unless you decide to act on it.

Before you start

Who it's for

Developers and code reviewers who use AI to write code and want a quick, history-based sanity check before merging.