Vee3 MCP server for Cursor — website screenshot capture
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vee3-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# vee3-mcp MCP server for [Vee3](https://vee3.io) — capture website screenshots from Cursor Agent. ## Cursor setup 1. Install [uv](https://docs.astral.sh/uv/getting-started/installation/) 2. Create an API key at [app.vee3.io/dashboard/keys](https://app.vee3.io/dashboard/keys) 3. Set `VEE3_API_KEY` in your environment 4. Use the **Add to Cursor** button on the dashboard, or add to `~/.cursor/mcp.json`: ```json { "mcpServers": { "vee3": { "command": "uvx", "args": ["vee3-mcp"], "env": { "VEE3_API_URL": "https://api.vee3.io", "VEE3_API_KEY": "${env:VEE3_API_KEY}" } } } } ``` ## Environment variables | Variable | Required | Default | |---|---|---| | `VEE3_API_KEY` | Yes | — | | `VEE3_API_URL` | No | `https://api.vee3.io` | ## Publish to PyPI From the repo root, after setting `PYPI_API_TOKEN`: ```powershell cd mcp uv build uv publish --token $env:PYPI_API_TOKEN ``` Then set `NEXT_PUBLIC_MCP_USE_PYPI=true` on Vercel so the dashboard install link uses `uvx vee3-mcp` instead of the Git source.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.