AppVeyor MCP for AI. Control your entire CI/CD stack from plain text.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
AppVeyor MCP lets your AI agent control complex DevOps tasks. You can manage CI/CD builds, update user roles, add new projects, and audit entire environments using simple text commands.
It gives you complete system visibility for managing pipelines and team access without navigating multiple web dashboards.
What AI agents can do with AppVeyor Automation
Add collaborator
Adds a new external person to work on projects within AppVeyor.
Add project
Creates and registers a completely new project in your account.
Add role
Defines an entirely new organizational role with specific permissions.
List all active projects or retrieve the history for any given project to track build status and configuration changes.
Add, delete, update user accounts, and manage organizational roles, ensuring proper security permissions across the board.
Start new builds, cancel failing deployments immediately, or force a re-run of any project's pipeline.
Handle external collaborators by listing their access levels, adding them, or removing them completely from the account.
Ask an AI about this
Waiting for input…
What AI agents can do with AppVeyor: 28 Available Tools
These tools allow you to perform every major function in AppVeyor, from creating new users to triggering emergency builds, all through simple text prompts.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using AppVeyor on VinkiusAdd Collaborator
Adds a new external person to work on projects within AppVeyor.
Add Project
Creates and registers a completely new project in your account.
Add Role
Defines an entirely new organizational role with specific permissions.
Add User
Creates and adds a brand-new internal user account to the system.
Cancel Build
Immediately stops a build that is currently running, useful for preventing bad code...
Cancel Deployment
Stops an active deployment process before it reaches production.
Delete Collaborator
Removes an external collaborator's access entirely from the system.
Delete Project
Permanently removes a project and all associated resources.
Delete Role
Removes an organizational role that is no longer needed for the team.
Delete User
Permanently removes a user account from AppVeyor.
Get Collaborator
Retrieves all details for one specific collaborator using their unique ID.
Get Environment Settings
Fetches the current configuration settings for a specified environment, like staging or production.
Get Project History
Retrieves the full timeline of changes and events that occurred within a project over time.
Get Project Last Build
Retrieves the status and details of a project's most recent build attempt.
Get Project Settings
Retrieves the current configuration parameters and settings for a specific project.
Get Role
Gets all details about a specified role using its unique ID number.
Get User
Retrieves the full profile and status of a specific user based on their ID.
List Collaborators
Returns a list containing every external collaborator currently connected to your account.
List Environments
Lists all defined deployment environments (e.g., dev, staging, prod).
List Projects
Provides a full list of every project registered in your AppVeyor account.
List Roles
Returns a complete list of all existing organizational roles and permission sets.
List Users
Provides an exhaustive list of every user account connected to your AppVeyor...
Rerun Build
Re-run a build
Start Build
Initiates a brand new, fresh build for a specified project.
Start Deployment
Begins the deployment process for a defined project and environment.
Update Collaborator
Modifies the access rights or details of an existing external collaborator account.
Update Role
Changes the permissions associated with a defined organizational role.
Update User
Updates specific profile details or status for an existing user account.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The AppVeyor integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with AppVeyor, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by AppVeyor. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 28 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Headache of Cross-Platform DevOps Management, Solved with Vinkius AI Gateway
Today, managing a modern application stack means jumping between AppVeyor's web dashboard, your identity provider, and ticketing systems. To update permissions for a developer, you might have to log into one place, copy the user ID, switch to another tool to check their current role, and then return to a third place just to confirm they can see the right project list.
With this MCP, that whole sequence collapses. You tell your agent exactly what needs changing—for instance, 'Update John Doe's role so he can access the staging environment.' The agent handles retrieving his ID (get_user), checking current permissions (list_roles), and applying the update (update_role) without you ever touching a dashboard.
AppVeyor MCP: Full Control Over Your Pipelines
You eliminate the manual steps of checking build status, manually initiating deployments, and tracking which environment was last updated. These repetitive clicks are replaced by simple commands like start_build or cancel_deployment.
What's different now is that your entire DevOps workflow runs through natural language conversation. You get immediate confirmation on every change, turning a complex, multi-step process into one conversational exchange.
What your AI can actually do with this
This connector links your AppVeyor account to any AI client, turning complex DevOps tasks into plain language requests. Instead of clicking through menus to check build statuses or update permissions, you simply ask your agent to do it.
It lets you manage the entire lifecycle of your deployments from one spot. You can list all existing projects and review their configurations. Need to onboard a new team member? You don't need to manually add them; you can use the tools to create user accounts, assign them specific roles, and grant access to only the necessary projects.
Security audits are painless. Your agent handles querying current role assignments or checking which external collaborators have access. If something breaks in a pipeline, you can ask it to list all environments or even trigger an immediate build re-run. For full catalog management like this, Vinkius provides a unified way to connect these services to your preferred AI client, keeping everything centralized.
019ea5e0-2c20-7029-acf7-e569feacf382 
Here's how it actually works
The bottom line is that you get a single command interface for managing every aspect of your DevOps stack.
Subscribe to this MCP on Vinkius and provide your AppVeyor API Token.
Connect your agent to this MCP in your preferred AI client.
Tell your agent what you need done, like 'List all projects' or 'Cancel the production deployment'.
Who is this actually for?
This MCP is built for operations teams and infrastructure engineers who spend too much time switching between dashboards. It solves the problem of needing real-time visibility into build status, user access, and deployment health without writing boilerplate API scripts.
Runs automated onboarding tasks, such as calling add_user and then using list_projects to confirm the new account has visibility into the correct repositories.
Performs rapid compliance checks by listing all users and checking their role assignments or verifying collaborator access rights.
Manages team structure quickly, using tools like add_role to create a new permission set, then updating an existing user with the new privileges.
What Changes When You Connect
Audit compliance instantly. Instead of manually checking permissions across multiple tabs, use the list_users and list_roles tools to query every user's current role assignment in one go.
Stop manual restarts. If a deployment fails at 3 AM, don't waste time logging in. Use cancel_deployment or rerun_build directly via your agent to fix it instantly.
Simplify onboarding. When adding a new developer, simply use add_user and then update_role to assign them the minimum necessary permissions without giving them blanket admin access.
Track everything easily. Need to know why a build failed last week? Get project history or get_project_last_build to retrieve that data immediately for debugging.
Manage external partners securely. Instead of email chains, use list_collaborators and update_collaborator to manage every outside user's access in one workflow.
See it in action
The Quick Security Audit
A security officer needs to confirm that all contractors have been removed from the staging environment. They ask their agent to list_collaborators and then cross-reference that list with get_user details to verify no deleted accounts are still active.
Fixing a Broken Release
A deployment fails right before going live. The engineer asks the agent to cancel_deployment immediately, preventing bad code from reaching production. They then use start_build to trigger a fresh attempt.
Onboarding a New Team Member
The team lead adds_user for a new hire and assigns them the proper access level using add_role, ensuring they only see projects relevant to their department. They then use get_project_settings to confirm visibility.
Reviewing Project Changes
A developer needs to understand why a feature broke. Instead of digging through logs, they ask the agent to get_project_history and analyze every recorded change leading up to the failure.
The honest tradeoffs
Using separate tools for user actions
Manually going through the web interface, clicking 'Users,' finding John Doe's profile, and then manually selecting 'Change Role' to assign him a new permission set.
Just ask your agent to update_user and specify that you want to change his role. The system handles both retrieving John Doe’s details (get_user) and applying the change in one go.
Forgetting which projects exist
A manager asks for a report on 'the payment module,' but has no idea if that project was renamed or deleted.
First, run list_projects to get the definitive list of every active project. Then you can ask your agent to get details for the correct name.
Trying to guess build status
Assuming a deployment is done because someone sent an email saying 'it's deployed.' There’s no confirmation or record.
Use list_environments to confirm the available environments, and then use get_project_last_build to pull definitive data on the actual build status.
When It Fits, When It Doesn't
Use this MCP if your job requires controlling multiple interconnected systems—like user databases, CI/CD pipelines, and project repositories—all from a single text prompt. If you spend more than five minutes per week navigating different dashboards to check status or change permissions, this is for you.
Don't use this if you only need one simple thing, like just listing users, because that specific task could be handled by a simpler list_users tool alone. However, if your goal involves checking user roles and then updating a project setting based on those findings, you need the full power of this MCP.
Questions you might have
How do I use the AppVeyor MCP to check project status? +
Use list_projects first to see all available projects. Then, you can ask for get_project_last_build or get_project_settings to pull specific details on any single project.
Can the AppVeyor MCP help me onboard a new user? +
Yes. You first use add_user to create the account, and then you can assign them permissions using update_role or by adding them to specific projects with add_collaborator.
What if I need to stop a deployment that failed? +
Simply ask your agent to cancel_deployment. It will immediately halt the process and prevent further damage to the environment.
Does AppVeyor MCP allow me to manage roles for external partners? +
Yes. You can use list_collaborators to see who is outside your team, and then update_collaborator or delete_collaborator to modify their access.
Is the AppVeyor MCP only for new projects? +
No. It handles existing infrastructure too. You can list all environments using list_environments and check settings with get_environment_settings, regardless of project age.
We've already built the connector for AppVeyor. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 28 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.