AppVeyor MCP integration for AI agents.
Connect AI agents to AppVeyor through 6 structured actions, including get build artifacts, get environments, and get projects. Review authentication, inputs…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the AppVeyor integration exposes
The AppVeyor Agent App exposes 6 provider-backed actions for developer tools work. Its current contract lets an authorized agent list artifacts produced by one appveyor build job, list appveyor deployment environments accessible to the connected api token, and list appveyor projects accessible to the connected api token. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected AppVeyor account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AppVeyor capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_build_artifactsREADList artifacts produced by one AppVeyor build job.
INPUTS: accountName / jobId
get_environmentsREADList AppVeyor deployment environments accessible to the connected API token.
INPUTS: accountName
get_projectsREADList AppVeyor projects accessible to the connected API token.
INPUTS: accountName
get_roleREADRetrieve one AppVeyor team role by ID.
INPUTS: accountName / roleId
get_rolesREADList AppVeyor team roles accessible to the connected API token.
INPUTS: accountName
get_usersREADList AppVeyor team users accessible to the connected API token.
INPUTS: accountName
INPUT CONTRACTS
Know what the action needs before it runs.
get_build_artifacts
accountNameOPTIONAL- The AppVeyor account name used to scope requests for user-level API keys.
jobIdREQUIRED- The AppVeyor build job ID whose artifacts should be listed.
get_environments
accountNameOPTIONAL- The AppVeyor account name used to scope requests for user-level API keys.
get_projects
accountNameOPTIONAL- The AppVeyor account name used to scope requests for user-level API keys.
get_role
accountNameOPTIONAL- The AppVeyor account name used to scope requests for user-level API keys.
roleIdREQUIRED- The AppVeyor role ID to retrieve.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Build Artifacts
List artifacts produced by one AppVeyor build job. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_build_artifactsVerify with Get Environments
List AppVeyor deployment environments accessible to the connected API token. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_environmentsSAFETY BOUNDARY
Operate AppVeyor with explicit limits
- Authorize AppVeyor with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned AppVeyor data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in AppVeyor rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AppVeyor task completed successfully.
CONNECTION MODEL
API key
AppVeyor API token used with the Authorization Bearer header. Find or create it on the AppVeyor API token page: https://ci.appveyor.com/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by AppVeyor.