Appveyor
AppVeyor is a hosted continuous integration service for building and deploying applications.
Verdict
Common use cases
- Fetch artifact URLs after a build completes
- List deployment environments before a release
- Audit team roles and user permissions
- Check which projects are configured in CI
- Retrieve build logs for debugging failures
Integration
- Vendor
- Appveyor
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 6
- Composio slug
appveyor
Tools
- Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
- Get Environments
Tool to get a list of all deployment environments. use when you need to enumerate available environments before creating deployments.
- Get Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
- Get Role
Tool to retrieve details of a specific role. use when you need to inspect permissions and metadata of a role by id.
- Get Roles
Tool to retrieve all roles in the account. use when you need to enumerate available roles before assigning permissions.
- Get Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Find Appveyor in the MCP catalog and click Connect. 3. You'll be prompted to paste an Appveyor API key — generate one by logging into your Appveyor account, going to the API Keys section under your profile, and creating a new key with at least read permissions for projects, builds, and environments. 4. Paste the key into Switchy and click Authorize. 5. Return to any Space and type '@Appveyor get projects' to test the connection — you should see a list of your repositories. 6. To invoke a tool during a conversation, @mention Appveyor and describe what you need in plain language; the AI will map your request to the appropriate tool and return the data inline.
What teammates see: by default, memories from Appveyor are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Projects
@Appveyor show me all projects in our account, including the last build status for each one.Open in a Space →
Get Latest Artifacts
@Appveyor get the artifacts from the most recent build of the main branch in the api-gateway project.Open in a Space →
Check Deployment Environments
@Appveyor what deployment environments are configured right now and which ones are active?Open in a Space →
Audit User Roles
@Appveyor list all users in the account and tell me which roles are assigned to each person.Open in a Space →
Inspect Role Permissions
@Appveyor get the details of the 'Deployer' role and explain what permissions it includes.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@appveyor list all projects in our account and show me which ones have builds running right now
Found 8 projects in your AppVeyor account. Currently active: 'api-gateway' (build #342, commit a7f3c2, started 4 minutes ago) and 'mobile-app' (build #189, commit d9e1b5, started 12 minutes ago). Idle projects include 'legacy-monolith', 'data-pipeline', 'admin-dashboard', 'notification-service', 'auth-service', and 'reporting-worker'. This illustrative example shows how the MCP surfaces project status at a glance.
Demonstrates the Get Projects tool for account-wide visibility. Requires API key with read access to all projects. Build status reflects a point-in-time snapshot; rapidly changing builds may show stale data if polled too frequently against AppVeyor's rate limits.
@appveyor get the build artifacts from the latest successful build of the api-gateway project so I can download the deployment package
Retrieved artifacts from api-gateway build #341 (last successful, completed 2 hours ago). Available artifacts: 'api-gateway-v2.3.1.zip' (12.4 MB, deployment package), 'test-results.xml' (340 KB, unit test output), 'coverage-report.html' (1.2 MB, code coverage). Each artifact includes a direct download URL valid for 24 hours. This example illustrates how the MCP fetches deployment-ready files after a build completes.
Uses Get Build Artifacts to retrieve downloadable files from a completed job. Requires knowing the project name and build number (or querying recent builds first). Artifact URLs expire; download promptly or re-query if links are stale.
@appveyor show me all deployment environments and summarize which projects are configured to deploy to production versus staging
Found 4 deployment environments: 'production' (AWS us-east-1, 3 projects configured: api-gateway, mobile-app, auth-service), 'staging' (AWS us-west-2, 5 projects), 'dev' (Azure, 2 projects), and 'qa' (on-prem, 1 project). Production deployments require manual approval; staging is automatic on merge to main. This illustrative summary combines environment metadata with project deployment settings to map your release pipeline.
Pairs Get Environments with project configuration context to synthesize deployment topology. Useful for auditing release workflows before making changes. Requires API key with environment read permissions; does not show historical deployment logs or trigger new deployments.
Use-case deep-dives
When Switchy beats manual artifact checks after CI runs
A 5-person backend team ships microservices to staging three times a day. Their Appveyor builds generate Docker images, config files, and test reports—but nobody remembers to verify all three landed correctly until something breaks in QA. With Switchy, the team lead asks "show me artifacts from the last staging deploy for auth-service" during standup, and the MCP pulls the build job list in one query. This works because Appveyor's artifact API is fast and the team has under 20 active projects. If you're running 50+ projects or need to correlate artifacts across multiple CI systems, you'll hit the single-vendor wall—Switchy can't join Appveyor data with GitHub Actions or Jenkins in one query. For teams standardized on Appveyor who want artifact visibility without opening the web console, this is the call.
Faster environment checks before shipping to production
A 3-person DevOps rotation manages 12 deployment environments across dev, staging, and prod for a SaaS product. Before promoting a release candidate, they need to confirm which environments are active, who has deploy permissions, and whether staging configs match prod. Manually clicking through Appveyor's UI takes 8 minutes; asking Switchy "list all environments and show roles with deploy access" takes 15 seconds because the Get Environments and Get Roles tools return structured data the AI can parse. This scenario wins when you have under 20 environments and a stable permission model. If your environment count exceeds 30 or you're frequently rotating roles, the MCP's lack of diff or change-tracking tools means you'll still need a spreadsheet. For small teams doing weekly deploys with predictable environment topology, Switchy cuts the pre-flight checklist in half.
When new hires need CI visibility on day one
A 6-person startup onboards a junior engineer who needs read access to CI logs and build history but shouldn't touch production deploys. The engineering manager asks Switchy "show all users in Appveyor and their role assignments" to audit current permissions before adding the new hire. The Get Users and Get Roles tools surface the full account roster in one query, and the manager spots two contractors still listed from last quarter. This use case works because Appveyor's user API is simple and the team has under 15 accounts. If you're managing 40+ users or need to sync permissions across Appveyor, GitHub, and AWS, the MCP can't automate the cross-platform reconciliation—you'll export to CSV and pivot table it. For small teams doing quarterly access reviews or onboarding one person at a time, Switchy makes the audit conversational instead of a spreadsheet chore.
Frequently asked
What does the AppVeyor MCP let me do in Switchy?
The AppVeyor MCP connects your CI/CD pipeline data to Switchy's AI workspace. You can query build artifacts, list projects and deployment environments, inspect user roles, and pull team member lists — all without leaving your chat interface. It's useful for debugging failed builds or auditing permissions across projects.
Do I need admin access to connect AppVeyor?
You need an AppVeyor API key with read access to the resources you want to query. Account-level endpoints like Get Users and Get Roles typically require admin or owner permissions. Project-specific tools like Get Build Artifacts work with project-level API keys. Generate the key in AppVeyor's account settings before connecting.
Can the AppVeyor MCP trigger new builds or deployments?
No. This MCP is read-only. It retrieves build artifacts, lists environments, and inspects roles — but it won't start builds, cancel jobs, or deploy code. If you need write operations, use AppVeyor's REST API directly or their webhook integrations.
How is this different from checking AppVeyor's dashboard?
The MCP pulls AppVeyor data into Switchy's shared workspace, so your team can ask questions like 'show me artifacts from the last build' or 'which environments are configured' without switching tabs. It's faster for ad-hoc queries and combines with other MCPs — you can cross-reference build logs with GitHub commits in one conversation.
Who on the team should connect the AppVeyor MCP?
Whoever owns your AppVeyor account or has API key generation rights. Once connected, any Switchy workspace member can query the data the key permits. If you want to limit access to sensitive projects, create a restricted API key in AppVeyor first. The connection doesn't count against AppVeyor's user seats.