Conventional Commit Linter Connector for AI agents.
3 live capabilities
Waiting for input…
Why people use Conventional Commit Linter
See what Conventional Commit Linter changes in a real workflow.
Move from a question to a useful Conventional Commit Linter result without breaking your flow.
What Vinkius changes
Get the Conventional Commit Linter answer you need in the AI client you already use.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Check commit structure and type
Ensures every commit follows the standard format for types like feat, fix, or chore.
- Real-world use case 02
Identify breaking changes
Scans text for indicators of breaking changes to flag them for major version updates.
- Real-world use case 03
Analyze SemVer impact
Get the result without leaving the conversation.
Complete set · 3capabilities
The complete Conventional Commit Linter capability set.
These are the exact actions your AI can choose when you ask it to work with Conventional Commit Linter.
01—03
3 capabilities in this set.
Part of 3 available through Conventional Commit Linter.
- 01 Capability
Check commit structure and type
Ensures every commit follows the standard format for types like feat, fix, or chore.
- 02 Capability
Identify breaking changes
Scans text for indicators of breaking changes to flag them for major version updates.
- 03 Capability
Analyze SemVer impact
Set up in minutes
One URL. Then ask Conventional Commit Linter to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Conventional Commit Linter from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Conventional Commit Linter, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Conventional Commit Linter for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Conventional Commit Linter URL.
- Step 03
Save and start
Save the connection and enable Conventional Commit Linter in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"conventional-commit-linter": {
"url": "https://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Conventional Commit Linter
Open Agent mode in chat and ask: "Using Conventional Commit Linter, help me...". 3 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"conventional-commit-linter": {
"url": "https://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Conventional Commit Linter
Ask Copilot: "Using Conventional Commit Linter, help me...". 3 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"conventional-commit-linter": {
"url": "https://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Conventional Commit Linter
Open Cascade and ask: "Using Conventional Commit Linter, help me...". 3 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"conventional-commit-linter": {
"url": "https://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Conventional Commit Linter
Ask Cline: "Using Conventional Commit Linter, help me...". 3 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add conventional-commit-linter --transport http "https://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Conventional Commit Linter
Ask Claude: "Using Conventional Commit Linter, show me...". 3 tools are ready
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse Connectors
Git Atomic Operations Validator
Prevent destructive Git operations and enforce commit standards.
Git Branch Naming Linter
Validates git branch names against specific naming conventions and structural patterns.
SemVer Calculator
Validate, compare, and manipulate Semantic Versioning 2.0.0 strings.
Git Merge Conflict Resolver
Automatically identify and resolve Git merge conflict markers using deterministic strategies.
Gerrit
Manage code reviews via Gerrit. query changes and patch sets, handle reviewers and approvals, and audit project branches directly from any AI agent.
Code Climate
Manage code quality and engineering metrics via Code Climate. track repository grades, monitor snapshots, and audit test coverage directly from any AI agent.
Bring your own AI
Change the model, client or framework. Keep Conventional Commit Linter connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Conventional Commit Linter.
The practical details behind the request, access and result.
How does the linter validate a commit?
It analyzes the message structure using verify_commit_structure to check for type, scope, and description. Capabilities available: your_tool_name.
Can it identify breaking changes?
Yes, analyze_breaking_change_presence detects exclamation marks or BREAKING CHANGE footers.
How is the version impact determined?
The classify_release_impact capability calculates if the change requires a major, minor, or patch update.
One connection away
Give your agent a direct line to Conventional Commit Linter.
Connect Conventional Commit Linter once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available