Skip to main content
Glama
bswa006

AI Agent Template MCP Server

by bswa006

create_ide_configs

Generate IDE configurations for Cursor, VS Code, and IntelliJ to set up development environments with custom rules and debugging options.

Instructions

Create IDE-specific configurations for Cursor, VS Code, and IntelliJ

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to the project directory
analysisIdNoAnalysis ID from analyze_codebase_deeply
ideYesWhich IDE configurations to create
autoLoadContextNoEnable automatic context loading
customRulesNoCustom rules to add
includeDebugConfigsNoInclude debugging configurations

Implementation Reference

  • The primary handler function that orchestrates creation of IDE-specific configurations (Cursor, VSCode, IntelliJ) based on prior codebase analysis. Delegates to IDE-specific helper functions.
    export async function createIDEConfigs(
      config: IDEConfigConfig
    ): Promise<IDEConfigResult> {
      const result: IDEConfigResult = {
        success: false,
        filesCreated: [],
        message: '',
        recommendations: [],
      };
    
      try {
        // Check if analysis has been completed
        const analysisId = config.analysisId || global.latestAnalysisId;
        if (!analysisId || !global.codebaseAnalysis?.[analysisId]) {
          throw new Error('Codebase analysis must be completed first. Run analyze_codebase_deeply tool.');
        }
    
        const analysis: DeepAnalysisResult = global.codebaseAnalysis[analysisId];
        const ides = config.ide === 'all' ? ['cursor', 'vscode', 'intellij'] : [config.ide];
        
        for (const ide of ides) {
          switch (ide) {
            case 'cursor':
              await createCursorConfig(config, analysis, result);
              break;
            case 'vscode':
              await createVSCodeConfig(config, analysis, result);
              break;
            case 'intellij':
              await createIntelliJConfig(config, analysis, result);
              break;
          }
        }
        
        // Add general recommendations
        result.recommendations = generateIDERecommendations(analysis, config);
        
        result.success = true;
        result.message = `Created IDE configurations for ${ides.join(', ')}. ${config.autoLoadContext ? 'Auto-loading enabled.' : 'Manual loading required.'}`;
      } catch (error) {
        result.success = false;
        result.message = `Failed to create IDE configs: ${error}`;
      }
    
      return result;
    }
  • Input schema definition for the create_ide_configs tool, defining parameters like projectPath, analysisId, ide choice, and options.
      name: 'create_ide_configs',
      description: 'Create IDE-specific configurations for Cursor, VS Code, and IntelliJ',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description: 'Path to the project directory',
          },
          analysisId: {
            type: 'string',
            description: 'Analysis ID from analyze_codebase_deeply',
          },
          ide: {
            type: 'string',
            enum: ['cursor', 'vscode', 'intellij', 'all'],
            description: 'Which IDE configurations to create',
          },
          autoLoadContext: {
            type: 'boolean',
            description: 'Enable automatic context loading',
          },
          customRules: {
            type: 'array',
            items: { type: 'string' },
            description: 'Custom rules to add',
          },
          includeDebugConfigs: {
            type: 'boolean',
            description: 'Include debugging configurations',
          },
        },
        required: ['projectPath', 'ide'],
      },
    },
  • Registration and execution handler in the MCP CallToolRequest switch statement. Validates params with Zod and calls the createIDEConfigs function.
    case 'create_ide_configs': {
      const params = z.object({
        projectPath: z.string(),
        analysisId: z.string().optional(),
        ide: z.enum(['cursor', 'vscode', 'intellij', 'all']),
        autoLoadContext: z.boolean().optional(),
        customRules: z.array(z.string()).optional(),
        includeDebugConfigs: z.boolean().optional(),
      }).parse(args);
      
      const result = await createIDEConfigs(params);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Inline tool registration in the minimal server implementation for standalone use.
    {
      name: 'create_ide_configs',
      description: 'Create IDE-specific configurations for Cursor, VS Code, and IntelliJ',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: { type: 'string' },
          analysisId: { type: 'string' },
          ide: { type: 'string', enum: ['cursor', 'vscode', 'intellij', 'all'] },
          autoLoadContext: { type: 'boolean' },
          customRules: { type: 'array', items: { type: 'string' } },
          includeDebugConfigs: { type: 'boolean' },
        },
        required: ['projectPath', 'ide'],
      },
  • Usage of createIDEConfigs within the complete_setup_workflow tool as a supporting step.
    const ideResult = await createIDEConfigs({
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates configurations but does not explain what that entails—whether it modifies files, requires specific permissions, has side effects, or what the output looks like. This is inadequate for a tool that likely performs file system operations.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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

Completeness2/5

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

Given the tool's complexity (6 parameters, no output schema, and no annotations), the description is insufficient. It does not cover behavioral aspects, output expectations, or integration with siblings like 'analyze_codebase_deeply', leaving significant gaps for an agent to understand full context.

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 fully documents all parameters. The description adds no additional meaning beyond implying the tool handles multiple IDEs, which is already covered by the 'ide' enum. Thus, it meets the baseline for high schema coverage without compensating value.

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

Purpose4/5

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

The description clearly states the action ('Create') and target ('IDE-specific configurations for Cursor, VS Code, and IntelliJ'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'complete_setup_workflow' or 'initialize_agent_workspace', which might involve similar setup activities, so it lacks sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing an analysis ID from 'analyze_codebase_deeply'), exclusions, or contextual cues for selection among siblings, leaving usage ambiguous.

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/bswa006/mcp-context-manager'

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