Glossary of design MCP servers

MCP

Model Context Protocol, an open protocol that lets an AI app connect to outside servers and call the tools they expose.

MCP server

The service's end of an MCP connection. It exposes named tools that an agent can call. It can run locally on your machine or remotely at an address.

Design MCP

An MCP server whose tools return design material: templates, components or the contents of a design file. See what is a design MCP.

Client

The AI app that connects to MCP servers: a coding agent, an editor with an agent, or a chat app. The client runs the model and decides when a tool is called.

Tool

One action a server offers, with a name, a description and inputs. The agent reads the description to decide when to call it. You can steer that by naming the tool or the server in your request.

Remote server

An MCP server reached over the internet at an address, as opposed to a program the client starts on your machine. uberdesigner's server is remote, at https://uberdesigner.ai/api/mcp.

Streamable HTTP

The transport a remote MCP server commonly uses to talk to a client over the web. Some clients ask you to name it when adding a server.

OAuth sign-in

Signing in to a server through the service's own page in a browser, after which the client holds access on your behalf. It avoids copying an API key into a config file. See permissions and safety.

Custom connector

What chat apps call an MCP server you add yourself by pasting its address in settings. See design MCP for chat apps.

mcp-remote

A small bridge program, started with npx, that lets a client able to run only local servers reach a remote one. See the editors page.

Browse and get

The two steps of using a library server. Browsing reads the library in brief so the agent can suggest options. Getting takes one template by name, and on uberdesigner counts as taking the template.

Morph

Crossing two designs into one. uberdesigner's server has a tool for it that takes two links, screenshots, videos or files. See design morphing.