Since.dev MCP server
Commit Nov 14, 2026Enables AI agents to verify packages, AI models, and runtimes against recent changes before applying fixes or upgrades.
Also known as Since-dev/cursor
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 14, 2026
- License
- MIT
What is Since.dev MCP?
Since.dev enables AI agents to verify packages, AI models, and runtimes against recent changes before applying fixes or upgrades.
Summary generated from the project's README
About Since.dev MCP server
Verifying packages, AI models, and runtimes against recent changes before applying fixes or upgrades is the primary function of this MCP server. It is designed for developers using Cursor to ensure that automated changes do not conflict with recent updates in their environment. The setup requires adding the server via a deep link and signing in through a browser, or manually cloning the repository into the local plugins folder and reloading the window.
The server provides three specific tools: whats_changed and check_code, which are read-only, and fix_code, which initiates pull requests and requires user permission. It works alongside four specialized skills and a rule file to guide the agent. These components trigger checks when the agent encounters manifests, lockfiles, Dockerfiles, workflows, or runtime version files, ensuring the AI understands the current state of the system before it modifies code.
What you can do with it
- 1Verify environment before upgradesAsk the agent to check for recent changes in packages or runtimes before it attempts to upgrade any dependencies.
- 2Automated fix pull requestsRequest that the agent applies a fix by opening a pull request after verifying the necessary context.
Written from the project's README. Every use case is checked against a quote from it.
README
View on GitHubSince.dev for Cursor
The Since.dev plugin for Cursor: the MCP server, four skills and a rule, so the agent checks your packages, AI models and runtimes against what changed before it touches them, and gets the fix.
Install
Add to Cursor adds the server; sign in through your browser when Cursor asks. For the server, the skills and the rule together, clone this repository into Cursor's local plugins folder and run Developer: Reload Window:
git clone https://github.com/since-dev/cursor ~/.cursor/plugins/local/since-dev
Without the plugin, copy rules/since.mdc into .cursor/rules/ and the skills into
.cursor/skills/ in your repository.
What's inside
- The server at
https://api.since.dev/mcp: 3 tools.whats_changedandcheck_codeonly read;fix_codeopens fix pull requests, so Cursor asks before every call. - Skills:
since-before-upgrading,since-model-retirements,since-what-changed,since-ci-and-runtimes. They tell the agent when to check: before upgrades, when code names a model, before writing against something it learned in training, and when editing CI or runtimes. - A rule (rules/since.mdc) that attaches when a manifest, lockfile, Dockerfile, workflow or runtime version file is in context.
For Claude, Codex, Gemini and any other MCP client, see Since-dev/mcp. Documentation: https://since.dev/docs.
License
MIT. See LICENSE.
Since.dev MCP questions
What tools are included in the server?
The server provides three tools: whats_changed, check_code, and fix_code.
How do I install the Since.dev plugin for Cursor?
You can use the 'Add to Cursor' link to add the server and sign in via your browser, or manually clone the repository into Cursor's local plugins folder.
Does the fix_code tool make changes automatically?
No, the fix_code tool opens fix pull requests, which ensures Cursor asks for permission before every call.