Appveyor Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 28, 2026

CI pipeline monitoring for GitLab and GitHub - no API key.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets an assistant monitor CI pipelines for GitLab and GitHub, reportedly without an API key.

What you can do
  • Monitor CI pipelines for GitLab and GitHub from an assistant session.
  • The registry description gives only this monitoring purpose; no tool list, instructions or README are available, so the exact operations cannot be confirmed.
  • It runs as a local stdio process started from the npm package appveyor-mcp.
When to use it
Consider it when you want an assistant to keep an eye on GitLab or GitHub CI pipeline status during development work and you prefer a local, key-free setup. Because the available documentation is minimal, check the package itself before relying on it.
Requirements
Node.js and the npm package appveyor-mcp, run as a local stdio process on a desktop machine. No environment variables, headers or authentication are declared.
Before you install
The description claims no API key is needed, but nothing documents what credentials or tokens it may read from the local environment, and no tool list is published. Review the package source before installing, and note it is desktop-only and not available as a web executable.

Installation

In SourceWeft

  1. Open Appveyor Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 1, 2026
  2. v1.0.0Sep 24, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.