I'm assuming the OP is aware of a basic file copy but I believe their issue is they have the packages deployed into the MSDB.
To extract packages from the MSDB, you must first identify where in the msdb they exist. For that, you can query sysssispackagefolders and sysssispackages or you can just use my query SSIS Package Query
Armed with that query, the column of interest is the PackagePath column. Couple that with dtutil and you have an extract-o-matic for package recovery.
The base form of an extract from MSDB on localhost to the current folder in the file system would look like.
dtutil /sourceserver localhost /SQL "Package" /copy file;.\Package.dtsx
Run this query in Text mode (ctr-T) This query generates a series of dtutil calls which in turn extracts SSIS packages from a server.
WITH FOLDERS AS
-- Capture root node
cast(PF.foldername AS varchar(max)) AS FolderPath
PF.parentfolderid IS NULL
-- build recursive hierarchy
cast(F.FolderPath + '\' + PF.foldername AS varchar(max)) AS FolderPath
ON F.folderid = PF.parentfolderid
, PACKAGES AS
-- pull information about stored SSIS packages
P.name AS PackageName
, P.id AS PackageId
, P.description as PackageDescription
, suser_sname(P.ownersid) AS ownername
-- assumes default instance and localhost
-- use serverproperty('servername') and serverproperty('instancename')
-- if you need to really make this generic
'dtutil /sourceserver localhost /SQL "'+ F.FolderPath + '\' + P.PackageName + '" /copy file;.\' + P.PackageName +'.dtsx'
ON P.folderid = F.folderid
-- uncomment this if you want to filter out the
-- native Data Collector packages
-- F.FolderPath <> '\Data Collector'
Packages are just xml files. Just copy the files local, create a new empty project and then import the *.dtsx files into the project by using the Add Existing dialog choice from the Solution explorer.