AgentDock MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow host permissions and supported server integrations as the desktop or service changes

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Controlled local/remote computer, server, container and browser operations

What we know

Unified MCP runtime for files, commands, Git, dynamic MCP servers, browsers and task execution across machines/containers.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)fix(release): preserve prerelease Windows ProductVersion ( 207)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Files, commands, Git, browsers, desktop apps, Docker/deployment state. Writes: File writes; Commands; Git; Deployment operations.
Bearer/OAuth.
Sensitive access: Host files, Browser sessions, Credentials

Privileged environment-control runtime; endpoint exposure can confer host/container/browser authority.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,172 repository stars

Stars observed Oct 6, 2026.

No canonical package metric applied.

All limitations / Review context

What tool controls and MCP transports does AgentDock currently support?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Privileged environment-control runtime; endpoint exposure can confer host/container/browser authority.
Files, commands, Git, browsers, desktop apps, Docker/deployment state.
Bearer/OAuth.
Persists state/config/sessions under ~/.agentdock and can persist browser login state.
Reviewed write actions: File writes; Commands; Git; Deployment operations
Sensitive access: Host files, Browser sessions, Credentials
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Exact package install command
Pricing
Public deployments must use auth + HTTPS.
Authority can be very broad.

Original activity observations

2026-10-05T17:52:00Z: fix(release): preserve prerelease Windows ProductVersion ( 207)

Technical identity

github.com/uvwt/agentdock

Exact implementation source: https://github.com/uvwt/agentdock ↗
Reviewed resource type: Host
Repository identity: uvwt/agentdock
Service endpoint: http://127.0.0.1:8765/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
uvwt/agentdock
Recorded repository material and project history.

Setup · Watchlist

Host / Desktop app setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Download / install
Publisher instructions
AgentDock is a local/hosted MCP gateway with a management UI.
Configure application / integrations
MCP100 setup guide
Install OS package following https://uvwt.github.io/agentdock-docs/docs/getting-started/install. Then AgentDock Settings > Advanced connection to obtain local/remote MCP Streamable HTTP endpoint, authorize using Bearer token/OAuth and register it in your chosen client. Do not print/share bearer tokens.
Check connection
Suggested check
Confirm AgentDock is running and the client successfully lists server tools after authentication; open TCP port alone is insufficient.
Disconnect / uninstall / revoke
Suggested check
In AgentDock Connections/Settings disable the MCP endpoint or remove the local/public connector. Stop its service or Docker deployment; uninstall the host application with the original platform installer. Remove clients' Bearer credentials separately if necessary.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.

Official Documentation & Sources

What it does

Unified MCP runtime for files, commands, Git, dynamic MCP servers, browsers and task execution across machines/containers.

Capability: Cloud & DevOps
Resource type: Host
Industry: Software & Technology
Best fit: Controlled local/remote computer, server, container and browser operations

Representative uses

Run commands/edit files
Manage Docker/VPS/proxies
Operate authenticated web pages/macOS apps
Register dynamic MCP servers

Limitations

Public deployments must use auth + HTTPS.
Authority can be very broad.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Bearer/OAuth.
Permissions: Files, commands, Git, browsers, desktop apps, Docker/deployment state.
Data handling: Persists state/config/sessions under ~/.agentdock and can persist browser login state.
Cost: unknown
Risk and cautions: Privileged environment-control runtime; endpoint exposure can confer host/container/browser authority.

Access scope and cautions

Write actions: File writes Commands Git Deployment operations
Sensitive access: Host files Browser sessions Credentials
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Run commands/edit files; Manage Docker/VPS/proxies; Operate authenticated web pages/macOS apps; Register dynamic MCP servers.

What setup and authentication are documented?

Recorded endpoint: http://127.0.0.1:8765/mcp. Recorded transport: streamable_http, stdio. Prerequisites: Official package or Docker. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Bearer token or OAuth; public access must keep auth enabled.

Can it modify data or perform write operations?

Documented write actions include: File writes; Commands; Git; Deployment operations. Recorded permission boundary: Files, commands, Git, browsers, desktop apps, Docker/deployment state.

What data-handling boundary should I consider?

Persists state/config/sessions under ~/.agentdock and can persist browser login state. Recorded sensitive-access context: Host files; Browser sessions; Credentials.

What limitations and risks should I check before use?

Privileged environment-control runtime; endpoint exposure can confer host/container/browser authority. Public deployments must use auth + HTTPS. Authority can be very broad. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

uvwt is listed as Community implementation in MCP100’s current evidence.