Planning System MCP Server

Instructions

Implementation Reference

• src/tools.js:598-607 (handler)

  The handler function for the 'get_node_context' MCP tool. It extracts plan_id and node_id from arguments and makes an API call to retrieve the node's comprehensive context (including children, logs, and artifacts) from the backend endpoint `/plans/{plan_id}/nodes/{node_id}/context`, then formats the response.

  if (name === "get_node_context") {
    const { plan_id, node_id } = args;
    
    // Get node with context
    const response = await apiClient.axiosInstance.get(
      `/plans/${plan_id}/nodes/${node_id}/context`
    );
    
    return formatResponse(response.data);
  }

• src/tools.js:250-261 (registration)

  Registration of the 'get_node_context' tool in the ListToolsRequestHandler response. Includes the tool name, description, and input schema definition.

  {
    name: "get_node_context",
    description: "Get comprehensive context for a node including children, logs, and artifacts",
    inputSchema: {
      type: "object",
      properties: {
        plan_id: { type: "string", description: "Plan ID" },
        node_id: { type: "string", description: "Node ID" }
      },
      required: ["plan_id", "node_id"]
    }
  },

• src/tools.js:253-260 (schema)

  Input schema for the 'get_node_context' tool, defining required plan_id and node_id parameters.

  inputSchema: {
    type: "object",
    properties: {
      plan_id: { type: "string", description: "Plan ID" },
      node_id: { type: "string", description: "Node ID" }
    },
    required: ["plan_id", "node_id"]
  }