GLM-4.6 MCP Server

Instructions

Implementation Reference

• src/glm-client.ts:143-157 (handler)

  The primary handler function for the 'design_system_architecture' tool. It constructs a tailored prompt from the input requirements and delegates to the consultArchitecture method, which queries the GLM-4.6 API.

    async designSystemArchitecture(requirements: string): Promise<string> {
      const query = `Design a system architecture based on the following requirements:
  
  ${requirements}
  
  Provide:
  1. High-level architecture diagram description
  2. Component breakdown and responsibilities
  3. Data flow and communication patterns
  4. Technology stack recommendations
  5. Scalability and deployment strategy
  6. Security architecture considerations`;
  
      return this.consultArchitecture(query);
    }

• src/index.ts:65-78 (registration)

  Tool registration in the MCP tools list, including name, description, and input schema definition.

  {
    name: 'design_system_architecture',
    description: 'Design a complete system architecture based on requirements using GLM-4.6. Provides component breakdown, data flow patterns, technology recommendations, and deployment strategies.',
    inputSchema: {
      type: 'object',
      properties: {
        requirements: {
          type: 'string',
          description: 'Detailed system requirements, constraints, and objectives',
        },
      },
      required: ['requirements'],
    },
  },

• src/index.ts:172-183 (handler)

  MCP server request handler switch case that dispatches the tool call by extracting arguments and invoking the GLMClient handler.

  case 'design_system_architecture': {
    const { requirements } = args as { requirements: string };
    const response = await glmClient.designSystemArchitecture(requirements);
    return {
      content: [
        {
          type: 'text',
          text: response,
        },
      ],
    };
  }