vincent-vnc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VNC_HOST | No | VNC target (the server runs on the Mac Studio itself) | localhost |
| VNC_PORT | No | VNC port | 5900 |
| VNC_USER | Yes | The dedicated automation account's username | |
| AUTH_TOKEN | Yes | Bearer token / Basic-auth password for the viewer | |
| REPORTS_DIR | No | Fixed, shared location for structured test-run reports | ~/vncmcp_reports |
| VIEWER_HOST | No | Interface the viewer binds to — auto-detects Tailscale IP, falling back to 127.0.0.1 | auto-detected |
| VIEWER_PORT | No | Port for the viewer; install.sh picks a free port once and pins it in .env — set to 0 to go back to picking a new free port on every restart | fixed at install |
| VNC_PASSWORD | Yes | Its Screen Sharing password | |
| RECORDINGS_DIR | No | Base directory for per-run recordings/logs/screenshots | ~/vncmcp_runs |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cookiemonster0921/vincent-vnc-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server