setup-snapvisor
Skill0 starsChanged 9 days agoMITView on GitHub
Connects the SnapVisor MCP server to Claude and verifies it with one read-only call: where to connect in claude.ai, Claude Desktop, Cowork, or Claude Code, what the SnapVisor sign-in and consent screen asks, and how to recover when a tool is missing. Use when the user asks to 'set up SnapVisor', 'connect SnapVisor to Claude', 'install the SnapVisor connector', 'sign in to SnapVisor', 'why can't Claude see my SnapVisor data', 'SnapVisor tools are missing', or reports 'Tool not found' for a SnapVisor tool.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Never ask the user for a SnapVisor password, API key, or access token in the chat.
- Distinctive: line 51
Do not change SnapVisor settings on the user's behalf.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from plugins/snapvisor/skills/setup-snapvisor/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Set up SnapVisor
Connect the SnapVisor MCP server, confirm it answers, and fix the usual reasons a SnapVisor tool is missing. Sign-in and consent always happen in SnapVisor's own browser page, never in the chat.
- MCP server key:
snapvisor(tools are writtensnapvisor:<tool>) - MCP server URL:
https://mcp.snapvisor.io(streamable HTTP, OAuth 2.1 with PKCE) - Docs: https://snapvisor.io/docs/agents/mcp-server
Where to connect
Claude Code with this plugin
- The plugin already registers the
snapvisorserver. Run/mcp, pick the SnapVisor server, and choose Authenticate, or just ask a SnapVisor question and follow the sign-in link Claude opens. - Without the plugin, add the server by hand:
claude mcp add --transport http snapvisor https://mcp.snapvisor.io, then authenticate from/mcp. - A connector added on claude.ai is also available in Claude Code when you are signed in with the same claude.ai account, so there is no need to connect twice.
claude.ai, Claude Desktop, and Cowork
- Open the SnapVisor listing in the Connectors Directory: https://claude.ai/directory/connectors/snapvisor and select Connect. In the app you can also search the directory for "SnapVisor".
- Sign in to SnapVisor in the page that opens and approve the consent screen.
- On a Team or Enterprise plan, an Owner may need to approve the connector first; members without that permission see a Request button.
What the sign-in asks
SnapVisor asks you to sign in, then lets you choose which accounts and scopes this connection may use. MCP access needs the SnapVisor Pro plan. Builds and screenshots are uploaded by your CI, so Claude can read and review screenshots but cannot capture or upload one.
Verify the connection
Make one read-only call and report what came back in a sentence.
Call snapvisor:search_tools with a query such as me, then run snapvisor:execute_typescript with return await external_getMe({});. On a per-tool server, call snapvisor:getMe directly. It returns the signed-in user and the accounts this connection can reach. A normal answer means SnapVisor is connected; say so and continue with the user's task.
When a tool is missing
SnapVisor serves Code Mode by default: tools/list shows only snapvisor:search_tools and snapvisor:execute_typescript, and every operation is an external_<operation> function inside the sandbox.
- "Tool not found" on a named tool: switch to
snapvisor:search_toolsthensnapvisor:execute_typescriptinstead of retrying the direct call. snapvisor:search_toolsdoes not return the tool: its scope was not granted. Ask the user to disconnect and reconnect SnapVisor and approve that scope on the consent screen.- An error naming a setting or a plan: a SnapVisor setting or plan gate refused the call. Relay the message and any settings link it carries; do not retry around it.
- No
snapvisortools at all, or an authentication error: the connector is not connected or the sign-in expired. Repeat the steps under "Where to connect".
Rules
- Never ask the user for a SnapVisor password, API key, or access token in the chat. OAuth happens in the browser.
- Do not change SnapVisor settings on the user's behalf. Settings that unlock writes are turned on by a signed-in person in SnapVisor.
- The verification call reads only. Do not create, send, or publish anything while setting up.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

