# AppVeyor MCP > 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. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** ci-cd, automation, user-management, pipeline-tracking, devops ## Description 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. ## Tools ### 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. ### 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 from deploying. ### 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 instance. ### 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. ## Prompt Examples **Prompt:** ``` List all projects in my AppVeyor account. ``` **Response:** ``` I've retrieved your projects. You have 3 active projects: 'frontend-app', 'backend-api', and 'infrastructure-deploy'. Would you like details on any of them? ``` **Prompt:** ``` Show me all users and their current roles. ``` **Response:** ``` Fetching user list... I found 5 users. Most are assigned to the 'Developer' role, while 'admin@company.com' holds the 'Administrator' role. Should I list the specific permissions for the 'Developer' role? ``` **Prompt:** ``` Get details for user with ID 98765. ``` **Response:** ``` Inspecting user 98765... This user is 'John Doe', email 'john@example.com'. They were added on 2023-10-15 and currently have 'Collaborator' status. Would you like to update their role? ``` ## Capabilities ### Project and Environment Management List all active projects or retrieve the history for any given project to track build status and configuration changes. ### User and Role Administration Add, delete, update user accounts, and manage organizational roles, ensuring proper security permissions across the board. ### Build and Deployment Control Start new builds, cancel failing deployments immediately, or force a re-run of any project's pipeline. ### External Access Control Handle external collaborators by listing their access levels, adding them, or removing them completely from the account. ## Use Cases ### 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. ## Benefits - 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. ## How It Works The bottom line is that you get a single command interface for managing every aspect of your DevOps stack. 1. Subscribe to this MCP on Vinkius and provide your AppVeyor API Token. 2. Connect your agent to this MCP in your preferred AI client. 3. Tell your agent what you need done, like 'List all projects' or 'Cancel the production deployment'. ## Frequently Asked Questions **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.