# vCard Parser Alternative MCP

> vCard Contacts Parser Alternative reads messy iPhone and Android `.vcf` files instantly, converting them into clean, structured JSON. Stop asking your AI client to read raw contacts; it'll crash or hallucinate. This tool strips away all the binary noise and delivers exactly what you need: Name, Email, Phone, and Organization.

## Overview
- **Category:** productivity
- **Price:** Free
- **Tags:** vcard, contact-management, data-parsing, json-conversion, local-processing

## Description

You exported your address book, right? You get this massive `.vcf` file—a nightmare of legacy vCard structures and bloated base64 garbage. Sending that raw text to any standard AI client is a recipe for disaster; it'll burn through your context window fast and start hallucinating numbers or emails. Forget about letting an agent choke on messy contacts.

This MCP is your dedicated contact intelligence engine, period. It runs entirely local, so your phonebook never leaves your machine. You feed it the vCard file, and we convert that mess into a clean JSON array. Your AI client only ever sees exactly what you need: First Name, Last Name, Organization, Phone number, and Email address—nothing more.

For those who handle travel logistics, remember this tool can also process structured itinerary text, letting your agent identify segments like flights, hotel stays, transfers, and meals from day-by-day plans. But when you're dealing with contacts, here’s what you get:

When you run the parser, it first handles individual records by isolating and cleaning up details from single contacts within a massive file; this stops data bleed between entries so you don't accidentally mix John Doe's job title with Jane Smith's phone number. You can then ask your agent to pull specific emails—it scans the whole vCard dataset and hands you a clean, structured list of every valid email address it finds.

Need to know where people work? It pulls out company names and job titles, letting you filter contacts by department or employer without having to read the messy original record. You can query the entire local contact dataset—say, 'Find all contacts who live in Chicago'—without ever exposing the raw vCard structure to your agent. If you need to send this data somewhere else—like into a CRM—the tool handles it by converting the structured JSON right into a spreadsheet-ready CSV format for bulk imports and reporting.

It’s simple: You give it the chaos, and it gives you clean, actionable data points. Your agent uses these tools to perform complex tasks that standard LLMs just can't touch—it reads the messy vCard format, cleans it into JSON, extracts emails, identifies roles, searches by location, and spits it out as a CSV. You don’t waste tokens on garbage; you get pure data.

## Tools

### parse_travel_itinerary
Parses structured travel text, identifying segments like flights, hotel stays, transfers, and meals from day-by-day plans. Note: This tool handles itinerary text, not vCard files.

## Prompt Examples

**Prompt:** 
```
Search my contacts.vcf and give me a list of everyone who works at 'Vinkius'.
```

**Response:** 
```
I found 3 contacts working at Vinkius: John Silva (DevOps), Sarah Connor (Design), and Mike Ross (Legal).
```

**Prompt:** 
```
Extract all the email addresses from this vCard export and format them as a CSV.
```

**Response:** 
```
Name,Email
Alice Smith,alice@example.com
Bob Jones,bob@example.org
```

**Prompt:** 
```
Look through my contacts and find the phone number for 'Plumber'.
```

**Response:** 
```
The phone number saved under 'Plumber' is +1 (555) 019-8372.
```

## Capabilities

### Extracting specific email addresses
The tool scans the vCard data and returns a clean, structured list of all valid email addresses found in the contacts.

### Identifying organizational roles
It isolates company names and job titles from mixed contact records, allowing you to filter by department or employer.

### Searching by criteria
You can query the entire local dataset (e.g., 'Find all contacts who live in Chicago') without exposing the raw vCard structure.

### Formatting contact data as CSV
The tool converts the parsed JSON into a spreadsheet-ready format, perfect for bulk imports or reporting.

### Parsing individual records
It isolates and cleans details from single contacts within a massive file, preventing data bleed between entries.

## Use Cases

### Cleaning up a partner mailing list
A partnership manager downloads 1,000 contact records from an event. Instead of manually copy-pasting emails into a spreadsheet, they ask their agent to process the vCard file using the parser. The result is a clean CSV ready for immediate mail merge.

### Finding a specific executive's number
You need to call the VP of Marketing from your contacts list, but that name is buried among dozens of people. You ask your agent to search the vCard file and pull out only 'VP of Marketing,' getting the direct phone number instantly.

### Preparing data for a database migration
Your team needs to move all contacts into a new CRM that requires strict JSON formatting. The parser ingests the vCard, strips the proprietary noise, and outputs structured records ready for schema validation.

### Comparing company affiliations across leads
A sales rep gets 50 leads from different sources, each with a messy contact export. The parser ingests them all, allowing the agent to query: 'Which of these people work at TechCorp?' and get a precise list.

## Benefits

- Stops hallucination. Instead of your agent guessing a number, it pulls the exact phone number saved in the vCard file using the dedicated contact tools.
- Handles massive files. You can throw 5,000+ contacts at this server without worrying about running out of context window space.
- Maintains privacy. The processing runs locally on your machine; your raw address book never gets uploaded anywhere else.
- Saves time on data cleanup. It converts complex vCard syntax into simple fields (First Name, Last Name), letting you query immediately.
- Allows targeted searching. Ask your agent to 'Find all contacts at Acme Corp,' and it returns only the relevant list.

## How It Works

The bottom line is that instead of giving your AI raw phone data it can't read, you give it perfectly organized, machine-readable contact records.

1. You pass the raw `.vcf` contact export file to your AI client.
2. The MCP Server executes local parsing, stripping away vCard syntax and binary noise.
3. Your agent receives a clean JSON array containing only structured fields (Name, Email, Phone, Org) ready for use.

## Frequently Asked Questions

**Does vCard Contacts Parser Alternative handle all file types?**
No, it handles the specific `.vcf` (vCard) format exported from phones. It's not a general document parser; its strength is parsing messy contact card syntax.

**Is vCard Contacts Parser Alternative secure for personal contacts?**
Yes, it runs 100% locally on your machine. Your raw phonebook data never leaves your environment.

**How do I use the parse_travel_itinerary tool with this server?**
The `parse_travel_itinerary` tool is for travel text, not contacts. You must upload a vCard file to utilize the primary contact parsing functionality of the MCP Server.

**Can it handle more than 100 contacts?**
Yes, it supports massive files. It can process VCF exports containing thousands of contacts without losing data or hitting context limits.

**When using the parser, what structure does the resulting JSON use for contacts?**
The output generates a clean array of objects, where each object represents one contact. The schema includes specific keys like 'firstName', 'lastName', 'organization', and dedicated arrays for phone numbers and emails.

**If a single vCard entry has multiple phones or addresses, how does the parser handle them?**
It captures all unique pieces of contact information. Instead of losing data, it stores multi-valued fields in arrays. For instance, if a person has three phone numbers, they appear as an array of three separate entries under 'phoneNumbers'.

**Beyond flights and hotels, what specific segments can I identify with the parse_travel_itinerary tool?**
The tool is designed to spot several distinct activity types. It identifies transfers (like airport shuttles), scheduled meals, and general sightseeing activities, giving you a complete view of the day's schedule.

**How does the local processing affect the speed when parsing very large VCF files?**
Because it runs 100% locally without cloud API calls, the extraction is highly efficient. It processes thousands of contacts quickly by skipping the heavy overhead and binary noise found in raw vCard exports.

**Is my address book uploaded to the cloud?**
Never. The vCard parsing is executed completely local on your device. Only the extracted text representation is provided to the AI context.

**Does it support multiple contacts in a single file?**
Yes! It perfectly parses multi-vCard files exported from iOS, Google Contacts, or Android devices, handling thousands of entries seamlessly.

**What happens to the contact profile pictures?**
Profile pictures (PHOTO;ENCODING=b) are intentionally ignored and stripped during parsing to preserve AI context tokens and prevent crashes.