← Blog · AI and MCP

What is MCP? A designer's guide to connecting AI assistants to your tools

If you have used an AI assistant for design work, you have probably hit the same wall: it can talk about color, but it cannot check anything. Ask it for an accessible palette and it will give you hex codes it has never measured. Ask it whether two colors have enough contrast and it will guess. MCP is the standard that removes the guessing, by letting the assistant call a real tool and read the real answer.

The USB-C idea

The MCP project describes itself with a simple picture: MCP is to AI applications what USB-C is to devices. Before a common port, every gadget needed its own cable. Before MCP, every assistant needed its own custom integration for every tool. With MCP, a tool publishes one server, and any assistant that speaks the protocol can plug into it. The same Tintly server works in Claude Code, Cursor, VS Code and the others, with no per-assistant code on our side.

The three parts

The client

The assistant you talk to: Claude, Cursor, VS Code with Copilot, a command-line agent. It decides when a tool would help and asks the server to run it.

The server

A small program that offers tools. Tintly's server offers 13, such as generate_palette, check_contrast and describe_palette. It runs on our side, so there is nothing to install.

The tools

Named actions with a described input and a described result. The assistant reads the descriptions to learn what each tool is for, then fills in the inputs from your request.

What happens when you ask for a palette

  1. 1
    You ask in plain words

    For example: make me a calm palette for a banking app and check that the text is readable.

  2. 2
    The assistant picks tools

    It sees that generate_palette and check_contrast fit, and sends each one the inputs it worked out from your request.

  3. 3
    Tintly computes the answer

    Contrast is measured with the WCAG formula, not estimated. The server returns exact ratios and pass or fail for each level.

  4. 4
    The assistant explains the result

    You get a palette with real numbers behind it, and any failure comes with a closest passing color.

How an MCP server is reached

The protocol defines two standard ways for a client and a server to talk. With stdio, the client starts the server as a program on your computer and they exchange messages through standard input and output. With Streamable HTTP, the server runs as a web service and the client sends each message as an HTTP POST to a single address. Tintly uses the second, which is why you add a web address and a key instead of installing anything.

The specification also says servers should authenticate connections and must validate the Origin header, so a web page cannot quietly talk to a server through your browser. Tintly does both: every request needs your API key, and browser requests are accepted only from allowed origins.

What to check before you connect any MCP server

Try it with Tintly

Create a free key on the developer page, then follow the setup guide for your assistant. Each guide has the exact configuration to paste and three prompts to try. If your assistant is not listed, any client that supports remote servers over Streamable HTTP needs only two things: the server address and an Authorization header carrying your key.

Sources and further reading