Bring Yaml Parsing
to VS Code Copilot
Learn how to connect Markdown Frontmatter Harvester to VS Code Copilot and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Markdown Frontmatter Harvester MCP Server?
If you use a Knowledge Management system like Obsidian, Logseq, or Hugo, you likely use YAML 'frontmatter' at the top of your markdown files to track metadata like status: draft, tags: [idea, research], or date: 2024-01-01.
When you ask Claude, 'Which of my notes are marked as drafts and never published?', it fails because it can't read thousands of local files quickly. This MCP solves that by acting as a hyper-fast metadata librarian. It recursively scans your local folder, rips out only the YAML frontmatter from every file, and aggregates it into a clean JSON index. The AI can then instantly filter, sort, and query your entire knowledge base.
The Superpowers
- Vault-Wide Indexing: Turns scattered local markdown metadata into a unified database.
- Lightning Fast: Uses
fast-globandgray-matterto scan 1,000+ files in milliseconds. - Zero Config: Just give the AI the absolute path to your notes folder.
- 100% Air-Gapped Privacy: Your private journal entries and business notes never leave your machine.
Built-in capabilities (1)
Provide the absolute directory path. Scan a local directory of Markdown files (Obsidian/Hugo) and extract all YAML frontmatter tags, dates, and metadata
Why VS Code Copilot?
GitHub Copilot Agent mode brings Markdown Frontmatter Harvester data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 1 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Markdown Frontmatter Harvester in VS Code Copilot
Markdown Frontmatter Harvester and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Markdown Frontmatter Harvester to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Markdown Frontmatter Harvester in VS Code Copilot
The Markdown Frontmatter Harvester MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Markdown Frontmatter Harvester for VS Code Copilot
Every tool call from VS Code Copilot to the Markdown Frontmatter Harvester MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Does it send my entire note content to the AI?
No. To protect your privacy and save context tokens, it strictly extracts ONLY the YAML metadata block between the --- delimiters. The actual body text of your note is ignored.
Will this alter my Obsidian files?
Not at all. The parser operates in a strict read-only mode. It reads the files into memory to extract the metadata and never writes back to the disk.
Does it work with nested folders?
Yes! The engine uses recursive globbing to scan every single folder and sub-folder inside the path you provide.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Paddle
10 toolsManage billing, subscriptions, and transactions via Paddle — inspect customers, list products, pause recurring plans, and void transactions from any AI agent.
JumpCloud
10 toolsManage users, systems, and directories via JumpCloud API.
Clockify
8 toolsManage time tracking and projects via Clockify — track entries, monitor projects, and audit team hours directly from any AI agent.
Clientify
8 toolsManage sales and marketing via Clientify CRM — track contacts, monitor deals, and audit CRM activities directly from any AI agent.