Skip to main content
Glama
AbdurRaahimm

MCP Terminal & Git Server

by AbdurRaahimm

install_vue_project

Create a Vue.js project using Vite, configure templates (Vue or TypeScript), install dependencies, and open in VSCode for immediate development.

Instructions

Create a new Vue project using Vite and open it in VSCode

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameYesName of the Vue project
destinationYesDirectory where to create the project (e.g., ~/Desktop)
templateNoVite template to use
installDependenciesNoInstall dependencies after creating project (default: true)

Implementation Reference

  • The main handler logic for the 'install_vue_project' tool. It resolves the destination path, ensures the directory exists, creates a new Vite Vue.js project using 'npm create vite', optionally installs dependencies with 'npm install', opens the project in VSCode, and returns a success message with instructions.
    case "install_vue_project": {
      const { 
        projectName, 
        destination, 
        template = "vue-ts",
        installDependencies = true 
      } = args as {
        projectName: string;
        destination: string;
        template?: string;
        installDependencies?: boolean;
      };
      
      const destPath = resolvePath(destination);
      await ensureDirectory(destPath);
      
      // Create Vite Vue project
      const createCommand = `npm create vite@latest ${projectName} -- --template ${template}`;
      
      const { stdout: createOutput } = await execa(createCommand, {
        shell: true,
        cwd: destPath,
      });
      
      const projectPath = path.join(destPath, projectName);
      
      // Install dependencies if requested
      if (installDependencies) {
        const installCommand = "npm install";
        const { stdout: installOutput } = await execa(installCommand, {
          shell: true,
          cwd: projectPath,
        });
      }
      
      // Open in VSCode
      await openInVSCode(projectPath);
      
      return {
        content: [
          {
            type: "text",
            text: `Vue project "${projectName}" created successfully with Vite at ${projectPath}\n\n` +
                  `Template: ${template}\n` +
                  `Dependencies: ${installDependencies ? "Installed" : "Not installed (run npm install manually)"}\n` +
                  `VSCode: Opened\n\n` +
                  `To start development:\n` +
                  `  cd ${projectPath}\n` +
                  `  ${installDependencies ? "" : "npm install\n  "}npm run dev`,
          },
        ],
      };
    }
  • Input schema defining the parameters for the 'install_vue_project' tool: projectName (required), destination (required), template (enum: vue, vue-ts), installDependencies (boolean, default true).
    inputSchema: {
      type: "object",
      properties: {
        projectName: {
          type: "string",
          description: "Name of the Vue project",
        },
        destination: {
          type: "string",
          description: "Directory where to create the project (e.g., ~/Desktop)",
        },
        template: {
          type: "string",
          description: "Vite template to use",
          enum: ["vue", "vue-ts"],
        },
        installDependencies: {
          type: "boolean",
          description: "Install dependencies after creating project (default: true)",
        },
      },
      required: ["projectName", "destination"],
    },
  • src/index.ts:144-170 (registration)
    Tool registration in the ListTools response, including name, description, and inputSchema.
    {
      name: "install_vue_project",
      description: "Create a new Vue project using Vite and open it in VSCode",
      inputSchema: {
        type: "object",
        properties: {
          projectName: {
            type: "string",
            description: "Name of the Vue project",
          },
          destination: {
            type: "string",
            description: "Directory where to create the project (e.g., ~/Desktop)",
          },
          template: {
            type: "string",
            description: "Vite template to use",
            enum: ["vue", "vue-ts"],
          },
          installDependencies: {
            type: "boolean",
            description: "Install dependencies after creating project (default: true)",
          },
        },
        required: ["projectName", "destination"],
      },
    },
  • Helper function to open a project directory in VSCode, with fallback paths for the 'code' executable.
    async function openInVSCode(projectPath: string): Promise<void> {
      try {
        await execa("code", [projectPath]);
      } catch (error) {
        // If 'code' command fails, try common VSCode executable paths
        const vscodePaths = [
          "code",
          "/usr/local/bin/code",
          "/usr/bin/code",
          "C:\\Program Files\\Microsoft VS Code\\Code.exe",
          "C:\\Program Files (x86)\\Microsoft VS Code\\Code.exe",
        ];
    
        for (const codePath of vscodePaths) {
          try {
            await execa(codePath, [projectPath]);
            return;
          } catch {
            // Continue to next path
          }
        }
        
        throw new Error("VSCode not found. Please ensure VSCode is installed and 'code' command is available in PATH");
      }
    }
  • Helper function to resolve paths, handling '~' expansion to home directory.
    function resolvePath(inputPath: string): string {
      if (inputPath.startsWith("~")) {
        return path.join(os.homedir(), inputPath.slice(1));
      }
      return path.resolve(inputPath);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions creating a project and opening it in VSCode, but does not disclose behavioral traits such as whether it overwrites existing directories, requires specific permissions, handles errors, or has side effects like modifying system files. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('Create a new Vue project') and includes key details (using Vite, opening in VSCode) without unnecessary words. Every part of the sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (creating and opening a project), no annotations, and no output schema, the description is minimally adequate but lacks completeness. It covers the what but not the how or what happens next (e.g., success/failure indicators, project structure). For a tool with 4 parameters and mutation behavior, more context would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description does not add any meaning beyond what the schema provides, such as explaining parameter interactions or default behaviors. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Create a new Vue project using Vite and open it in VSCode'), including the technology stack (Vue, Vite) and the post-creation action (open in VSCode). It distinguishes from sibling tools like install_react_project and install_next_project by specifying Vue, and from open_in_vscode by including project creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for Vue project creation with Vite, but does not explicitly state when to use this tool versus alternatives like install_react_project or git_clone. It provides context (creating Vue projects) but lacks explicit exclusions or comparisons to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AbdurRaahimm/mcp-git-terminal-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server