# vCard Contacts Parser MCP for AI Agents AI Agent Connect

> vCard Contacts Parser converts massive .vcf contact exports into structured JSON. It turns your AI into a hyper-intelligent local address book, letting you query names, phone numbers, and emails without hitting context limits or risking your privacy. It strips away the binary noise and base64 images that usually break LLMs.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_UUVXVBrUXJKoPBhQl9ZiqadlLzKKax2Ki7xxjJ7w/ai-agent-connect
- **Tags:** vcard, contact-parsing, data-extraction, address-book, json-conversion, file-processing

## Description

When you export your phone's address book, you usually end up with a bloated .vcf file. These files are often full of junk like base64-encoded images and legacy formatting that make it nearly impossible for an AI to read accurately. If you try to feed that raw file into your AI client, it will likely exhaust its context window or start hallucinating phone numbers and emails. This Connector acts as a dedicated contact intelligence engine. It runs 100% local on your machine, stripping away the binary noise and converting the raw vCard format into a clean JSON array. Your AI then sees exactly what it needs: First Name, Last Name, Organization, Phone, and Email. It is a great way to give your agent a searchable directory of your real-world connections without the headache of manual data cleaning or the risk of uploading your personal data to a third-party service. You can find this in the Vinkius catalog to get your local address book ready for your AI client. It handles files with thousands of contacts, making it perfect for people with huge networks who need to find specific info quickly. Because it works locally, your personal phonebook never leaves your machine. You get perfect extraction of country codes and company roles every time, ensuring your agent provides accurate answers.

## Tools

### parse_kindle_clippings
This tool parses your vCard files into a structured JSON format. It makes your contact list searchable for your AI client without needing to upload your data to the cloud.

## 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)
* **Mike Ross** (Legal)
```

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

**Response:** 
```
Here are the emails from your export:

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

### Convert .vcf files to JSON
Turn messy phone exports into clean data for your AI.

### Strip base64 image data
Remove binary noise that wastes your AI's context window.

### Extract specific contact fields
Get only the names, emails, and phones you actually need.

### Handle large contact lists
Process files with thousands of contacts in one go.

### Keep data processing local
Keep your personal phonebook on your machine for total privacy.

## Use Cases

### Finding a specific lead's phone number
A sales rep has a file of 5,000 leads and asks their agent to find the number for the CTO of a specific company.

### Extracting all emails for a CSV
A user wants to grab every email address from a vCard export and have their agent format them into a clean CSV file.

### Searching for company colleagues
A manager asks their agent to list everyone in their contacts who works at a specific organization.

### Querying for specific job titles
A freelancer asks their agent to find the contact info for anyone in their phonebook listed as a plumber.

## Benefits

- Keep your phonebook private by processing everything on your own hardware using the local parser.
- Stop your AI from hallucinating by providing clean JSON instead of raw vCards with the parse_kindle_clippings tool.
- Process thousands of contacts at once without hitting context window limits on your AI client.
- Get accurate extraction of country codes and company roles every time you query your list.
- Quickly find specific people like the CTO of a company using natural language queries.

## How It Works

The bottom line is you get a clean, searchable contact list without the mess of raw vCard files.

1. Point your AI client to your .vcf contact file.
2. The Connector parses the file and strips out the binary noise.
3. You get a queryable JSON list of all your contacts.

## Frequently Asked Questions

**Can I use the vCard Contacts Parser with my existing iPhone contacts?**
Yes. You just need to export your contacts as a .vcf file from your phone and point your AI client to that file.

**Will my personal phonebook stay private with this Connector?**
Yes. This Connector runs 100% locally on your machine. Your personal data is never sent to the cloud or shared with any third party.

**Can it handle thousands of contacts at once?**
Yes. It is designed to handle massive files with thousands of entries, making it much more efficient than pasting text into a chat.

**Does it work with both Android and iPhone vCard files?**
Yes. It supports the standard vCard structure used by both major mobile platforms.

**How does this help my AI client find people faster?**
By converting the file to a clean JSON array, your AI doesn't have to sift through binary noise or image data, which speeds up its response time.

**Do I need to manually clean my vCard files first?**
No. The Connector handles the cleaning for you by stripping out the unnecessary junk and base64 images automatically.

**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.