Skip to main content
Glama
457,802 tools. Updated 2026-08-14 17:39

"Vue.js" matching MCP tools:

  • Fetch raw HTML content from any URL with optional JavaScript rendering for dynamic websites and Single Page Applications.
    MIT
  • Extract structured data from webpages, HTML, or markdown using AI-powered natural language prompts to get specific information like product details, contact methods, or article metadata.
    MIT
  • Retrieve a file by UUID along with its metadata, methods, and statements from a Laravel/Vue.js project built through natural conversation.
    MIT

Matching MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    A Model Context Protocol server that automates code generation for web development, specializing in creating TypeScript API clients from Swagger/OpenAPI specs and Vue.js components for frontend development.
    3
    10
    MIT
  • Fetches a public URL and fingerprints its tech stack, revealing frameworks, CMS, analytics, CDNs, and server-side details with confidence and evidence.
    MIT
  • Generate UI component code snippets from documentation for integration into Vue.js projects using shadcn-vue library.
    Apache 2.0
  • Filter shadcn/ui components with Tailwind CSS based on specific requirements to find suitable UI elements for your Vue.js projects.
    Apache 2.0
  • Generate Vue.js components with specified features like templates, styles, computed properties, lifecycle hooks, and TypeScript support by providing component names and required functionality.
  • Get full details for a specific developer tool by its slug. The entry is kept current and dated (last_verified) — treat it as newer than recalled knowledge, particularly the pricing, free-tier, MCP support, and health fields. Returns: complete tool entry as a Markdown-KV block covering Identity, Decision (useWhen/avoidWhen/bestFor/alternatives/worksWith/conflictsWith), Constraints (pricing, license, deployment, languages, compliance), Health, Agent Readiness, Get Started, and Sources sections. Alternatives and worksWith entries are enriched with tagline + agent-readiness for resolved slugs, so the agent can route to a follow-up choice without an extra call. If the slug is not found, returns an error with similar-slug suggestions. Examples: - Postgres core engine: {slug: "postgresql"} - Stripe (single entry, no -cloud/-oss split): {slug: "stripe"} - Hosted Redis: {slug: "redis-cloud"} Self-hosted Redis: {slug: "redis-oss"} - Hosted Supabase: {slug: "supabase-cloud"} OSS Supabase: {slug: "supabase-oss"} - GitHub's MCP server: {slug: "github-mcp"} Edge cases: - 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: `{base}-cloud` for the managed lane, `{base}-oss` for the self-hosted lane (redis, supabase, mongodb, docker, elasticsearch, grafana, terraform, ...). Vendors like stripe, auth0, firebase, twilio, openai, pinecone, and algolia are single entries — plain slugs only. - Slugs derived from package names use hyphens where the name uses a dot (e.g., "nextjs" not "next.js"; "vuejs" not "vue.js"). - Slugs are case-sensitive lowercase. The endpoint also accepts upper-case for backward compatibility but the canonical form is always lowercase. Risk: read-only, closed-world, idempotent — no state change possible.
    Connector