Integrations: MCP server and GitHub Action

MCP server for coding agents

Your agent can check what's current before it writes code: the latest SDK version, whether a model is retired, and the guide for a breaking upgrade. It only reads. In Claude Code:

claude mcp add --transport http versyka https://www.versyka.com/api/mcp

Cursor, VS Code, Claude Desktop and others

Open Cursor Settings → MCP, click Add new MCP server and paste this into mcp.json:

{
  "mcpServers": {
    "versyka": {
      "url": "https://www.versyka.com/api/mcp"
    }
  }
}

Ask in the Agent chat.

With GitHub Copilot Chat, create .vscode/mcp.json:

{
  "servers": {
    "versyka": {
      "type": "http",
      "url": "https://www.versyka.com/api/mcp"
    }
  }
}

Click Start above the entry, then ask in Agent mode.

Open Settings → Connectors → Add custom connector, name it Versyka and paste:
```
https://www.versyka.com/api/mcp
```
Turn it on from the tools menu in a chat, then ask.

Any other assistant that supports remote MCP servers takes the same address with the Streamable HTTP transport. For every project on this computer in Claude Code, add --scope user.

What you can ask

check_dependenciesWhich API SDKs in a manifest are major versions behind or deprecated. “Check my requirements.txt for outdated API SDKs.”
find_retired_modelsAI model IDs in your code that are retired or retiring. “Are any of the AI models in this repo being retired?”
lookup_modelWhether one model ID is retired, and its replacement. “Is gpt-4-0613 still supported?”
list_model_retirementsThe retirement calendar: shutdown dates and replacements. “Which Anthropic models retire in the next 90 days?”
get_sdk_versionsThe latest version of a package, and whether yours is deprecated. “What is the latest Stripe SDK for Node, and is ours deprecated?”
list_migration_guidesVersyka's SDK migration guides, by package. “Which migration guides does Versyka have for AWS?”
get_migration_guideOne migration guide: what changed and the code before and after. “Upgrade this file from openai 0.28 to 1.x. Use the Versyka migration guide.”

GitHub Action

Checks every pull request, and once a week, for retired AI models and API SDKs that are major versions behind, and comments with the dates, replacements and the lines involved. Add this as .github/workflows/versyka.yml:

# .github/workflows/versyka.yml
name: Versyka
on:
  pull_request:
  schedule:
    - cron: "0 9 * * 1" # every Monday, so dates that come closer are caught too
permissions:
  contents: read
  pull-requests: write # to comment on pull requests; remove to only write the job summary
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: versyka/versyka-action@v1
        with:
          fail-on: retired # none | retired | soon | behind

Options

Input	Default	What it does
`fail-on`	retired	When to fail the check: none, retired (a model that no longer works), soon (retiring within days), or behind (also an SDK major versions behind or deprecated).
`days`	90	How many days ahead counts as "soon".
`comment`	true	Comment on the pull request. The comment is updated in place on every push, not repeated.
`path`	.	The folder to check, for monorepos.
`github-token`	github.token	Token used to comment. The default workflow token is enough.

Outputs: retired, soon and behind, the number of findings of each kind, for later steps. Source: github.com/versyka/versyka-action.

Your source code never leaves the Action's runner, and the MCP server only sees what your agent passes to a tool for that one call. Nothing is stored. More: Security.