Appveyor logo
ConnectorAppveyor

Appveyor integration for Claude and Codex

Create a Appveyor connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Appveyor from Claude

Add the Appveyor connection to a Space that runs Claude, then use it from every channel in that Space.

Use Appveyor from Codex

Add the Appveyor connection to a Space that runs Codex, then use it from every channel in that Space.

Use Appveyor from Sidekick

Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.

Developer Tools & IT

What the Appveyor connector can do

Appveyor runs continuous integration builds and deployments for software projects. In type.com, an engineering Space can ask Claude to pull a build log for debugging, check artifacts from a finished job, or delete an old build to clean up the project's history, all without opening a separate CI dashboard.

One connection, many Spaces

Connect Appveyor once, then decide which Spaces can use it in threads, skills, automations, and coding work.

What teams do with Appveyor in type.com

Debug a failed build without switching tabs

Pull the log from a specific build job to diagnose a failure right inside the conversation about it.

Try asking
Download the Appveyor build log for job 4821 so we can see why it failed.

Grab artifacts from a finished build

Check which artifacts a completed build produced before deciding what to deploy or archive.

Try asking
Get the Appveyor build artifacts for our latest release build and list what's available.

Clean up old builds

Remove builds that are no longer needed to keep the project's build history manageable.

Try asking
Delete this old Appveyor build by ID, it was from a test branch we no longer use.

Representative actions

  • Delete Build

    Removes a build from Appveyor by its ID.

  • Download Build Log

    Retrieves the log output for a specific build job.

  • Get Build Artifacts

    Lists the artifacts produced by a specific build job.

  • Get Build By Version

    Retrieves details about a project build using its version identifier.

  • Get Environments

    Lists all deployment environments available before creating a new deployment.

Connection

API and auth details

AppVeyor provides REST APIs for CI/CD automation, including teams, users, roles, collaborators, projects, builds, environments, deployments, artifacts, build triggering, build worker API calls, account-scoped API access, JSON/XML responses, and bearer-token authentication with account API tokens.

FAQ

Questions people ask before connecting Appveyor

Can Claude check CI builds in Appveyor?

Yes. With an Appveyor connection shared to your Space, ask Claude in a thread to pull build logs, check artifacts, or clean up old builds.

How does type.com authenticate with Appveyor?

Appveyor uses an API key tied to an account token. An admin adds it once when creating the connection and controls which Spaces can access build data through it.

Can type.com alert the team when a build fails?

The agent can check build status and logs whenever asked. For an ongoing check tied to deployments, set that up as a type.com automation that posts updates to a channel.

Is this the same as a Appveyor MCP server?

Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More developer tools & it connectors

All Developer Tools & IT integrations