Caisey

com.helpforsupportPublished by helpforsupport.comOfficial publisherv1.0.0Updated Oct 29, 2026

Troubleshoot enrolled client PCs from your AI client, with human approval and an audit trail.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an AI client troubleshoot enrolled client PCs, with human approval and an audit trail.

What you can do
  • Troubleshoot enrolled client PCs from the AI client.
  • Work under human approval, with an audit trail of actions.
  • No tool list is published, so the exact diagnostic and remediation actions are not documented in the registry entry.
When to use it
When you support managed or enrolled Windows-style client PCs and want an assistant to help diagnose and resolve issues on them, while keeping a human in the loop and a record of what was done.
Requirements
A remote MCP endpoint at helpforsupport.com over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared. Devices must already be enrolled with the provider.
Before you install
The server acts on enrolled client PCs, so its tools may change or fix machines; the description states human approval and an audit trail are part of the flow, but the specific actions are not listed. OAuth grants access to your enrolled devices, so review the scopes requested at sign-in.

Installation

In SourceWeft

  1. Open Caisey in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.helpforsupport%2Fcaisey/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "caisey": {
      "type": "http",
      "url": "https://helpforsupport.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.