Agentation MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Structured page annotations and visual feedback for coding agents: Does element feedback retain accurate source targeting when the page changes between annotation and agent edits?

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

Best fit

Turning browser visual feedback into structured tasks for coding agents.

What we know

Local MCP + HTTP server connecting Agentation visual annotations to coding agents, with session/state management and watch workflows.

Maintenance / activity evidence

agentation-mcp 1.3.2 published 2026-09-22T02:42:22.112Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Annotation/session state only. Writes: Create/update/delete annotation state; Acknowledge/resolve/dismiss/reply.
Authentication not yet verified.
Sensitive access: Page annotations, Feedback sessions

Local-by-default and comparatively narrow, but remote binding or webhook delivery widens exposure.

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

Popularity

· 356.8k package downloads / 30 days

Downloads observed Sep 25, 2026.

Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.

All limitations / Review context

Does element feedback retain accurate source targeting when the page changes between annotation and agent edits?

The bounded review of the publisher's documented Structured page annotations and visual feedback for coding agents and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Local-by-default and comparatively narrow, but remote binding or webhook delivery widens exposure.
Annotation/session state only.
State persists to local SQLite by default; configured webhooks can send event JSON externally.
Reviewed write actions: Create/update/delete annotation state; Acknowledge/resolve/dismiss/reply
Sensitive access: Page annotations, Feedback sessions
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Default HTTP service is loopback-only.
Remote/container binding needs explicit host/CORS configuration.
Webhooks are best-effort and add external data flow.

Original activity observations

agentation-mcp 1.3.2 published 2026-09-22T02:42:22.112Z

Technical identity

npm/agentation-mcp

Exact implementation source: https://www.npmjs.com/package/agentation-mcp ↗
Reviewed resource type: MCP Server
Repository identity: benjitaylor/agentation
Package identity: agentation-mcp
Service endpoint: http://localhost:4747

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 7, 2026

Package registry ↗
agentation-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
benjitaylor/agentation
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
The `server` subcommand is required; `doctor` is publisher diagnostic; browser-origin checks are not authentication
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
The `server` subcommand is required; `doctor` is publisher diagnostic; browser-origin checks are not authentication | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions
claude mcp add agentation -- npx -y agentation-mcp server
Configure / authenticate
MCP100 setup guide
Install the browser-side Agentation runtime in the target app as described in its install guide. MCP registration alone does not activate browser annotations.
Check connection
Suggested check
`npx agentation-mcp doctor` tests services; check client tools and browser annotation delivery separately.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `agentation`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove agentation

Official Documentation & Sources

What it does

Local MCP + HTTP server connecting Agentation visual annotations to coding agents, with session/state management and watch workflows.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Turning browser visual feedback into structured tasks for coding agents.

Representative uses

List sessions and pending annotations
Acknowledge/resolve/dismiss/reply
Watch new annotations
Receive browser-toolbar annotation events

Limitations

Default HTTP service is loopback-only.
Remote/container binding needs explicit host/CORS configuration.
Webhooks are best-effort and add external data flow.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Annotation/session state only.
Data handling: State persists to local SQLite by default; configured webhooks can send event JSON externally.
Cost: free
Risk and cautions: Local-by-default and comparatively narrow, but remote binding or webhook delivery widens exposure.

Access scope and cautions

Write actions: Create/update/delete annotation state Acknowledge/resolve/dismiss/reply
Sensitive access: Page annotations Feedback sessions
Risk level: moderate

FAQ

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

Which tasks are documented for this implementation?

The reviewed tasks include: List sessions and pending annotations; Acknowledge/resolve/dismiss/reply; Watch new annotations; Receive browser-toolbar annotation events.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y agentation-mcp server. Recorded endpoint: http://localhost:4747. Recorded transport: stdio, http. Prerequisites: Node.js 20+. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No auth documented; loopback and origin restrictions are the primary boundary.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete annotation state; Acknowledge/resolve/dismiss/reply. Recorded permission boundary: Annotation/session state only.

What data-handling boundary should I consider?

State persists to local SQLite by default; configured webhooks can send event JSON externally. Recorded sensitive-access context: Page annotations; Feedback sessions.

What limitations and risks should I check before use?

Local-by-default and comparatively narrow, but remote binding or webhook delivery widens exposure. Default HTTP service is loopback-only. Remote/container binding needs explicit host/CORS configuration. Webhooks are best-effort and add external data flow. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Agentation is listed as First-party MCP in MCP100’s current evidence.