AiLinkAny

io.github.zhangduochuanPublished by GitHub account zhangduochuanv1.0.0Updated Nov 7, 2026

Control your authorized Windows computers via OAuth: files, shell, apps, and task status.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant control your authorized Windows computers over OAuth: files, shell, apps and task status.

What you can do
  • Work with files on connected Windows machines
  • Run shell commands on those machines
  • Launch and manage applications
  • Check the status of tasks it started
  • All access is scoped to computers you have authorized through OAuth
When to use it
Useful when you want an assistant to operate your own Windows PCs remotely — inspecting or moving files, running commands, opening apps or checking on long-running tasks — without installing a local server.
Requirements
A remote MCP endpoint at mcp.ailinkany.com reached over streamable HTTP, with OAuth sign-in required. At least one Windows computer must be authorized to the service. No environment variables or headers are declared.
Before you install
The server can run shell commands and change files and applications on your machines, so actions may be destructive or hard to undo. Grant access only to machines you own or administer, and review what the OAuth authorization covers. No tool list is published, so the exact scope of each capability is not documented here.

Installation

In SourceWeft

  1. Open AiLinkAny 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/io.github.zhangduochuan%2Failinkany/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": {
    "ailinkany": {
      "type": "http",
      "url": "https://mcp.ailinkany.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.0LatestNov 7, 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.