by sammcj
Data Extractor converts JavaScript and TypeScript code into JSON configuration files using JSON stringify for better mai
Extracts embedded data like i18n translations and configurations from TypeScript/JavaScript code into separate JSON files. Also extracts SVG components from React files into individual .svg files.
Data Extractor is a community-built MCP server published by sammcj that provides AI assistants with tools and capabilities via the Model Context Protocol. Data Extractor converts JavaScript and TypeScript code into JSON configuration files using JSON stringify for better mai It is categorized under productivity, developer tools. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
You can install Data Extractor in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Data Extractor is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We evaluated Data Extractor against two servers with overlapping tools; this profile had the clearer scope statement.
Data Extractor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired Data Extractor into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Data Extractor is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired Data Extractor into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: Data Extractor surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Data Extractor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Strong directory entry: Data Extractor surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated Data Extractor against two servers with overlapping tools; this profile had the clearer scope statement.
Data Extractor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 40
Data Extractor converts JavaScript and TypeScript code into JSON configuration files using JSON stringify for better mai
TL;DR: Extracts embedded data like i18n translations and configurations from TypeScript/JavaScript code into separate JSON files. Also extracts SVG components from React files into individual .svg files.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
