Skip to content
  1. Getting started
  2. MCP server

MCP server

Let your coding agent read the kit: the real files of every component, in React or Vue, instead of a guess.

Trelund runs a Model Context Protocol server at https://trelund.com/mcp. Once your editor knows about it, your agent can list the components, read the files of the one you ask for and set up the accent tokens, the same files the Installation sections of these pages show. No account, no key.

Claude Code

Run this once in your terminal:

claude mcp add --transport http trelund https://trelund.com/mcp

Cursor

Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "trelund": {
      "url": "https://trelund.com/mcp"
    }
  }
}

VS Code

Add the server to .vscode/mcp.json in your project:

{
  "servers": {
    "trelund": {
      "type": "http",
      "url": "https://trelund.com/mcp"
    }
  }
}

Any other client that speaks MCP over HTTP works the same way: point it to https://trelund.com/mcp.

Tools

The server exposes three read-only tools. Your agent picks them on its own, you never call them by name.

get_setup

What a project needs before the first component, for React or Vue: Tailwind CSS v4, the packages to install and the accent tokens to declare next to your @theme.

list_components

Every component and layout of the kit, by category, with the slug to ask for.

get_component

The files of one component for React or Vue, the packages they import and the other components they rely on, so the agent fetches those too.

Try it

Ask in plain words and name the kit, the agent does the rest:

Set up Trelund in this project, then build the settings page with the sidebar layout.

Add a Trelund dialog to confirm the deletion of a project, in Vue.

Replace our date input with the Trelund date range picker.