AppVeyor MCP. Manage CI/CD, users, and roles via chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
AppVeyor gives your AI agent direct control over your CI/CD pipelines, user roles, and project lifecycle. Use natural language commands to list projects, add or delete users, manage permissions (`add_role`, `update_user`), and audit entire environments without ever opening the web dashboard.
What your AI agents can do
Add collaborator
Registers a new external team member to work on a project.
Add project
Creates a brand-new software development project space in AppVeyor.
Add role
Defines and adds a new permission set (a role) for users to adopt.
Start new builds, cancel live deployments, and check the history of any project using tools like start_build or cancel_deployment.
Add, delete, update, or retrieve specific user details by ID to maintain accurate team records.
Create new roles (add_role) and manage existing role definitions to control what users can actually do on the platform.
Add or remove external team members by managing their access levels through add_collaborator or delete_collaborator.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
AppVeyor: 28 Tools for DevOps Management
These tools let you manage every aspect of your CI/CD pipeline—from adding a user to cancelling an environment deployment—using simple, direct chat commands.
019ea5e0add collaborator
Registers a new external team member to work on a project.
019ea5e0add project
Creates a brand-new software development project space in AppVeyor.
019ea5e0add role
Defines and adds a new permission set (a role) for users to adopt.
019ea5e0add user
Creates an account for a new internal team member.
019ea5e0cancel build
Stops an ongoing, active build pipeline immediately.
019ea5e0cancel deployment
Rolls back or halts a running software deployment process.
019ea5e0delete collaborator
Removes an external collaborator's access entirely from the system.
019ea5e0delete project
Permanently removes an entire project and all its associated build history.
019ea5e0delete role
Deletes a defined role, removing it from all users who might have been assigned it.
019ea5e0delete user
Permanently removes an internal user account and their access credentials.
019ea5e0get collaborator
Retrieves all current details for a specific external collaborator using their ID.
019ea5e0get environment settings
Fetches the configuration settings for a specified deployment environment (e.g., staging or production).
019ea5e0get project history
Retrieves a full log and history of all builds and deployments for a project.
019ea5e0get project last build
Gets the status, time, and success status of the most recent build run for a project.
019ea5e0get project settings
Retrieves all core settings—like branch names or required variables—for a specific project.
019ea5e0get role
Retrieves the full definition and list of permissions for an existing role by its ID.
019ea5e0get user
Retrieves all personal details, status, and assignment information for a specific user ID.
019ea5e0list collaborators
Generates a list of every external collaborator currently attached to the account.
019ea5e0list environments
Outputs a list of all active deployment environments available in the system.
019ea5e0list projects
Provides a complete list and basic status overview of every project account holds.
019ea5e0list roles
Lists every defined role in the system, allowing you to see all available permission types.
019ea5e0list users
Generates a comprehensive list of every internal user account and their current status.
019ea5e0rerun build
Re-run a build
019ea5e0start build
Start a new build
019ea5e0start deployment
Start a deployment
019ea5e0update collaborator
Update an existing collaborator
019ea5e0update role
Modifies the permissions associated with an existing role definition.
019ea5e0update user
Changes details or status for an already existing user account.
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 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
AppVeyor gives your AI agent direct control over your CI/CD pipelines, user roles, and project lifecycle. You'll use natural language commands to manage everything without ever opening a web dashboard.
Managing Project Pipelines (CI/CD)
You can start builds using start_build or immediately re-run the last build with rerun_build. If something goes wrong, you can stop an active deployment process right away with cancel_deployment, and you can also halt a running build pipeline instantly via cancel_build. To see what happened before, use get_project_history to pull a full log of every build and deployment for any given project.
You'll always know the status and time of the most recent attempt by calling get_project_last_build. When you need an overview, run list_projects to get a list of every project account has, or use it to fetch specific core settings like branch names with get_project_settings. If a whole project is done, you can wipe it clean and permanently remove the entire space using delete_project.
Controlling Internal User Identity
You handle your internal team records using these tools. To bring someone onto the roster, use add_user to create an account for a new member. Need to change their status or details? Use update_user on an existing ID. If they leave, you can permanently remove their access credentials by calling delete_user.
You never forget who's on your team; run list_users to get every single internal user account and check their current status. To see specific info about one person, use get_user with an ID.
Governing Security Roles and Permissions
This server lets you control what people can actually do on the platform. You define a new permission set (a role) using add_role, or if a role is deprecated, delete it entirely with delete_role. To understand an existing rule, use get_role to retrieve its full definition and list of permissions by ID.
If you change what users can do, modify the ruleset using update_role. You'll see every permission type available in the system when you run list_roles.
Handling External Collaborators
You manage external partners through specific tools. To let a new team member work on your project, use add_collaborator. Need to cut off access? Use delete_collaborator to remove an external collaborator's credentials entirely. You can see every external person attached to the account by calling list_collaborators. If you need to update their profile or access level, run update_collaborator.
To pull all current details for a specific partner, use get_collaborator with their ID.
How AppVeyor MCP Works
- 1 Subscribe to the AppVeyor server and provide your API Token.
- 2 Instruct your AI client what needs fixing (e.g., 'I need to delete John Doe's account').
- 3 Your agent executes the necessary tool calls (like
delete_user) and reports the resulting state.
The bottom line is, you manage complex DevOps tasks using natural language commands instead of clicking through multiple dashboards.
Who Is AppVeyor MCP For?
Security Officers who need to audit access logs instantly. DevOps Engineers tired of manually updating user permissions across five different tools. Team Leads who need to onboard new developers and define their roles without calling the platform admin.
Runs builds, cancels deployments, and uses get_project_last_build to quickly check if a pipeline succeeded before notifying the team.
Audits who has access by running list_users combined with list_roles, ensuring every account adheres to corporate policy.
Adds new developers and defines their baseline permissions using tools like add_user and add_role in one chat session.
What Changes When You Connect
- Stop clicking through dashboards. Use
list_projectsto get a full overview of every project's status in one command, instantly. - Maintain compliance by running
get_userorget_collaboratorchecks whenever you need to verify who has access and what their current role is. - Eliminate manual onboarding. Use
add_userfollowed immediately byadd_roleto provision a new developer account with the exact permissions they need. - Fast incident response means less friction. If a build fails, use
get_project_last_buildand thencancel_deploymentwithout touching the GUI. - Audit security changes instantly. Running
list_rolesfollowed byget_rolelets you confirm if a permission change was applied correctly before it causes an issue.
Real-World Use Cases
The Offboarding Protocol
A developer leaves the company. Instead of having IT manually navigate 10 screens, the security team runs get_user to confirm details, then executes delete_user, and finally calls list_collaborators to ensure all external access is cut immediately.
Defining a New Tier
The project needs a 'QA Reviewer' role. A team lead uses add_role to create the permissions, then runs list_users and executes update_user for 15 people to assign that new role, all in one session.
Investigating a Broken Build
A build fails mysteriously. A DevOps engineer calls get_project_history to see the timeline, checks get_environment_settings for variables, and then uses list_environments to narrow down where the failure happened.
Growing the Team Scope
The company acquires a new partner. The team lead uses add_collaborator to bring in the external group, and then calls update_collaborator later when their access needs to change from 'Read-Only' to 'Contributor'.
The Tradeoffs
Manual User Sync
Copying user IDs and role names into a spreadsheet, then manually logging into AppVeyor to update every single account individually.
→
Don't touch the UI. Use list_users to get all accounts, then use your agent to run bulk commands like update_user or add_role across the entire list.
Ignoring Project Status
Assuming a project is healthy because it was created last week. Finding out later that no one has touched the code base.
→
Always run get_project_last_build and check the status. If the status is old or failed, you need to troubleshoot before proceeding.
Forgetting Cleanup
Deleting a user account but forgetting to remove their associated collaborator access, leaving orphaned records.
→
After deleting a user via delete_user, always run list_collaborators and confirm the external accounts are also cleaned up.
When It Fits, When It Doesn't
Use this server if your primary pain point is managing lifecycle state—creating, modifying, or destroying resources (users, roles, projects) in an automated way. If you need to audit a change that happened 3 weeks ago and just need a report, get_project_history works great. However, if all you ever need is read-only access to view data without changing anything, consider whether a dedicated reporting API (like a BI tool connector) might be better than using these write tools like add_role or delete_user. This server gives you full control; don't use it just for viewing if simpler reading APIs exist.
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
Works with 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 server provides 28 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Managing team access shouldn't require navigating six different dashboards.
Right now, updating a single user account means logging in, finding the user by email, clicking into their profile, going to the 'Roles' tab, selecting the new permission set, saving, and then repeating that process for every other project they touch. It’s tedious, error-prone, and takes forever.
With this MCP server, you just tell your agent: 'Update user John Doe's role to QA Reviewer.' The system executes `update_user` followed by the necessary permission changes instantly. You get clean status confirmation back in seconds.
AppVeyor MCP Server lets you manage all project resources from a single command.
Before this, checking if a build was ready meant manually navigating to the AppVeyor site, finding the correct project, clicking 'History', and then scrolling through potentially hundreds of entries to find the status marker. It’s high-friction reading.
Now, you ask for it: 'What's the last build status for the API backend?' The agent runs `get_project_last_build` and spits out a direct answer. You get immediate facts without any unnecessary UI clicks.
Common Questions About AppVeyor MCP
How do I check all my projects using list_projects? +
Run the list_projects tool. It outputs every project name and its current basic status, giving you a quick inventory of your entire account.
Can I delete a user with delete_user? +
Yes, running delete_user permanently removes the specified internal user account. Be sure to confirm they aren't needed before executing this command.
What is the difference between list_users and get_user? +
list_users gives you a comprehensive roster of everyone in the system. Use get_user when you already know the specific user ID and just need their detailed profile information.
How do I add a new collaborator? (add_collaborator) +
Use the add_collaborator tool, providing the external person's credentials and specifying which project they should have access to. This adds them without manual UI work.
What if I need to change a user’s role? (update_user) +
You use update_user by providing the user ID and specifying the new roles or permissions they should have. The tool handles updating their access rights.
What does `get_project_history` provide, and how do I view past build statuses? +
It retrieves a full log and timeline for the project. You get detailed steps showing which jobs passed or failed over time, letting you pinpoint exactly when an issue started.
Using `get_environment_settings`, what data can I collect about my deployments? +
This function returns all defined environmental variables for your account. You access things like specific branch names, service endpoints, and any custom configuration settings used during deployment.
If I use `delete_project`, does it affect linked resources or collaborators? +
It removes the entire project structure from your account. Be aware that deleting a project also revokes access for all associated collaborators and immediately stops any ongoing builds.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Infisical
Manage secrets infrastructure via AI — list, create, update, and audit secrets across environments with end-to-end encryption.
Supabase Alternative
Manage Supabase projects, databases and secrets via API — create projects, configure Postgres, manage branches and secrets from any AI agent.
Mailsac
Manage disposable and private email addresses via the Mailsac REST API.
You might also like
Buildkite
Automate CI/CD pipelines via Buildkite — manage builds, agents, and deployments directly from any AI agent.
Axonaut
All-in-one ERP and CRM automation — manage invoices, quotes, tasks, and company relationships via AI.
Gift Up!
Manage gift card orders, track balances, and process redemptions via AI agents with Gift Up!.