Vueuse Mcp

io.github.kovoorPublished by GitHub account kovoorv1.0.0Updated Oct 24, 2026

Search, browse, and get suggestions for VueUse composables

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets a coding assistant search VueUse composable documentation, read full docs, and get suggestions while writing Vue code.

What you can do
This local MCP server exposes VueUse documentation to an AI coding agent. Tools include search_composables for ranked keyword or concept search, get_composable_docs for full signatures, types, options, examples and related functions, suggest_composable for natural-language use cases with trade-offs, and list_categories for categories with composable counts. The agent calls these on its own while helping you write code.
When to use it
Useful when you write Vue code with VueUse and want the assistant to reference correct APIs, options and types instead of guessing. Best for projects already using VueUse or planning to, and for agents that can call tools during coding sessions.
Requirements
Runs locally over stdio, typically launched with npx vueuse-mcp, so Node.js and npm are needed. No authentication, environment variables or headers are declared for normal use. A GITHUB_TOKEN is only mentioned for refreshing scraped data during development.
Before you install
The bundled composable data is scraped from the VueUse GitHub repository, so it can lag behind the latest release; refreshing it requires running scrape and build steps. The optional GITHUB_TOKEN is only for avoiding rate limits while scraping. No write, send or delete actions are described.

Installation

In SourceWeft

  1. Open Vueuse Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

VueUse MCP

MCP server that gives AI coding agents instant access to VueUse documentation — search composables, read docs, and get suggestions.

How It Works When You Code

This is an MCP (Model Context Protocol) server. When you connect it to an AI coding agent like Claude Code, the agent can automatically look up VueUse documentation while helping you write code.

For example, if you ask "help me track the mouse position in Vue," the agent will:

  1. Call search_composables or suggest_composable to find relevant composables
  2. Call get_composable_docs to read the full documentation for useMouse
  3. Write code using the correct API, options, and types — without you needing to look anything up

You don't need to manually call any tools. The agent decides when to use them based on your questions.

Quick Start

Claude Code

bash
claude mcp add vueuse-mcp -- npx vueuse-mcp

Codex CLI

Add to your MCP config:

json
{  "servers": {    "vueuse": {      "command": "npx",      "args": ["vueuse-mcp"]    }  }}

OpenCode

Add to your opencode.json:

json
{  "mcp": {    "vueuse": {      "command": "npx",      "args": ["vueuse-mcp"]    }  }}

Available Tools

ToolDescription
search_composablesSearch by name, keyword, or concept. Returns ranked results with descriptions.
get_composable_docsGet full docs for a composable — signature, types, options, examples, related functions.
suggest_composableDescribe a use case in natural language and get ranked suggestions with trade-offs.
list_categoriesList all categories with composable counts. Optionally filter by package.

Keeping Data Fresh

The composable data is scraped from the VueUse GitHub repo. To update:

bash
npm run scrape && npm run build

Set a GITHUB_TOKEN environment variable to avoid rate limits during scraping. See .env.example.

Development

bash
git clone https://github.com/kovoor/vueuse-mcp.gitcd vueuse-mcpnpm installnpm run scrape    # fetch composable data from GitHubnpm run build     # compile TypeScriptnpm start         # run the server

Contributing

See CONTRIBUTING.md for how to add tools, update the scrape pipeline, and submit PRs.

Source: README.md at commit c0339d4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts