mcp
Technical notes on web development, DevOps, and AI integration.
10 articles
- 01:05testing
Token AI Leaked from Browser Snapshots, Not from My Tests
I thought my tests were expensive. Every browser action was returning a fresh accessibility snapshot into the agent's context instead.
TL;DR: The agent was using too many tokens due to taking accessibility-tree snapshots on every action. This was fixed by changing how the agent watched tests run. The solution involved limiting the agent's access to test results.
#playwright#vitest#mcp - 19:56testing
The Confirmation That Disappears: Wisata Admin QA
A QA session hit a delete click that vanished without deleting anything. The Playwright dialog contract explains why.
TL;DR: The disappearing confirm dialog wasn't an app bug; Playwright auto-dismisses native dialogs when no handler is registered, so destructive actions must go through the MCP browser_handle_dialog tool. Testing also found phone validation missing in two modules, folded into one cross-module ticket instead of two. Lesson: verify against tool contracts and database artifacts, not impressions.
#playwright#testing#mcp - 14:45ai
Where MCP Config Lives: User or Project Scope
Where MCP configuration belongs: workspace files travel with the repo and get team review, user profiles stay personal and skip review entirely.
#mcp#vscode#security - 14:45ai
When to Retire an AI Agent from Your Workflow
An objective evaluation framework for retiring AI agents: OWASP excessive agency root causes, MCP authorization audits, and operational retirement signals.
#ai#security#mcp - 03:42devops
A Zero-Diff Commit: Removing a Third-Party Integration
The commit removed an integration and changed zero lines of code. The real cleanup lives in credentials, caches, breakers, and billing.
TL;DR: A zero-diff commit declared a Plane integration removed, but the real cleanup happened entirely outside the codebase. Credentials, client caches, billing entitlements, and circuit breaker configs all outlive the code and need manual revocation. The lesson: treat integrations as detachable backing services and write a removal plan listing vendor touchpoints from day one.
#plane#api#mcp - 11:32devops
Do Not Use Absolute URLs for Plane Comment Image Embeds
Image embeds in Plane API comments fail hard on absolute URLs (401). Verified pipeline: in-container helper, image-component node, raw asset_id.
TL;DR: Using absolute URLs for Plane comment images always returns 401 because assets must load through an authenticated local proxy. Instead create the comment first, upload via the in-container helper, and embed with the native image-component node using only the raw asset ID. Remember updates replace all HTML so resend full content and verify rendering in the browser not with curl.
#plane#mcp#docker - 08:23devops
Bypassing the MCP Limit: Images in Plane Comments
The Plane MCP server has no upload action and the SSRF guard rightly rejects private URLs. The self-host answer: drop one level and create the FileAsset inside the container.
TL;DR: The Plane MCP server can't upload files and its SSRF guard correctly blocks loopback URLs and internal API keys. The workaround is a tiny Python script that copies the image into the container and uploads it to MinIO via Django shell. Then you patch the comment's HTML with the returned URL, which renders in the UI but stays private.
#plane#mcp#docker - 13:37ai
One small patch in plane-mcp to make it talk to Plane Community Edition
The /dependencies/ route 404s on CE self-hosted. A small fallback to the old /relations/ route fixes it.
TL;DR: The MCP link tool returned a bare 404 though the work items existed, because its cloud route is missing in Community Edition. The patch detects a missing-route 404 versus missing data and falls back to the older CE route with adjusted payloads. This keeps upstream merges simple and is validated by a live smoke test creating and linking real items.
#plane#mcp#ai - 13:21ai
Plane MCP is live: three operational gotchas you only feel after using it
No workspace delete via MCP, CORS reused as CSRF, and an API token sitting in .mcp.json next to the code.
TL;DR: Workspace deletion isn't exposed via API and requires double confirmation in the UI to prevent irreversible wipes by AI agents. CORS and CSRF share the single CORS_ALLOWED_ORIGINS variable, so adding an origin requires recreating all backend containers, not the proxy. API tokens sit in plaintext in .mcp.json, so you must gitignore the file and use expiring tokens.
#plane#mcp#ai