MCP server
Give a coding agent Teire's scan and catalog, so it checks the repository it is editing and looks up a provider's deprecations before it writes code against them.
teire mcp serves Teire's tools over stdio. The protocol uses stdout, and logs go to stderr.
If your agent uses skills, you can also install the Teire Agent Skill with npx skills add teire-dev/teire --skill teire-cli. The skill teaches the CLI workflow; connecting MCP gives the agent Teire's live tools.
claude mcp add teire -- npx -y teire-cli mcpTools
| Tool | Input | Returns |
|---|---|---|
scan_path | path (a folder, or a public GitHub repository as owner/name or its URL), optional fresh | The groups that need action, one per pull request Teire would open: verdict, priority, deadline, the version or model to move to and the first call sites. The rest are counted. Results are kept 5 minutes per path, unless fresh |
explain_finding | path, key (a group key, change ID or package name) | One group in full: its change records with summary, replacement, migration notes and quoted sources, and up to 50 call sites with their code, product code first |
list_changes | optional provider, ecosystem, kind, subject | Changes from the public catalog, or read on the spot from a provider's pages when the catalog doesn't hold them yet: ID, title, kind, class, date and replacement, 60 at a time |
get_change | id | One full catalog change record. For a package change computed during a scan, use explain_finding instead |
Every tool is marked read-only. None of them writes to the repository or to GitHub. A large repository takes a minute or two to scan; when the client asks for progress, each step is sent as a progress notification, which also keeps clients that reset their timeout on progress from giving up.
What an agent does with it
- Before an upgrade: call
scan_pathon the repository, thenexplain_findingon what it reports. The agent gets the lines to change and the change record: the computed API diff for a package, or the provider's quoted notice for a model or API change. - Before writing model code: call
list_changeswithprovider: "openai"(or any provider) to see which model IDs are retired or retiring, and what replaces them. - In review: call
get_changeon an ID from a Teire PR for the full record.
CLI
teire scan runs Teire's own engine on a folder or any public GitHub repository and prints every change that reaches your code, with its lines. teire check turns that into a CI gate.
Agent Skill
Give a coding agent Teire's scan workflow, then let the CLI or MCP server show the upstream changes that reach its code.