The search module makes extensive use of the api behaviour which is a request/response type context while meteor has a reactive paradigm.
Therefore, until a tighter meteor/semantic integration (including api) gets done, you can make use of the local search feature as documented.
You will then need to catch the keyboard events using Template.searchTemplate.events({}) and update the content array reactively.
For testing that and perhaps getting help from Jack and others, you can use
http://meteorpad.com which is basically jsfiddle for meteor.
$('.ui.search')
.search({
source: content
})
;
var content = [
{ title: 'Andorrs' },
{ title: 'United Arab Emirates' },
{ title: 'Afghanistas' },
{ title: 'Antigus' },
{ title: 'Anguills' },
{ title: 'Albanis' },
{ title: 'Armenis' },
{ title: 'Netherlands Antilles' },
{ title: 'Angols' },
{ title: 'Argentins' },
{ title: 'American Samos' },
{ title: 'Austris' },
{ title: 'Australis' },
{ title: 'Arubs' },
{ title: 'Aland Islands' },
{ title: 'Azerbaijas' },
{ title: 'Bosnis' }
// etc
];