Developer · Remote MCP server
Visily UI Design
UI design from prompts, screenshots, and URLs for AI coding agents and theme tokens.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.visily-app/visily- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-02
- Updated
- 2026-07-02
- Publisher
- visily-app (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/visily-app) · how
- Website
- www.visily.ai/
- Repository
- github.com/visily-app/mcp-plugins
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.visily.ai/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Visily UI Design
Visily UI Design is a remote MCP server: there is nothing to install. Its endpoint is https://app.visily.ai/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Vim MCPConnect Claude Code to Vim/Neovim - query state, execute commands, search help, record macros. | Local · stdio |
| VinktarProduct analytics and error tracking your coding agent can use. | Remote · HTTPLive check: sign-in required |
| VinvVinv runs, tests, and finds issues in your services - with zero code changes. | Local · stdio |
| Virtual FilesystemPostgreSQL-backed virtual filesystem for agents: session isolation, shared stores, POSIX ops, RLS. | Local · stdio |
| vivacProvenance tree for coding agents: where you are, why, and what was already decided. | Local · stdio |
| Vivado MCP NativeNative MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl. | Local · stdio |
| VivereKnow when cron jobs and AI agents stop running: create monitors and check in from your agent. | Remote · HTTPLive check: ✓ handshake |
| ViviooTrust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback. | Remote · SSELive check: ✓ SSE reachable |