
MCP Data Converter
io.github.igormilovanovicPublished by GitHub account igormilovanovicv1.4.3Updated Oct 24, 2026
Convert between 200+ format pairs: JSON, CSV, XML, YAML, PDF, Excel, DOCX and more.
Overview
Remote MCP server that lets an assistant convert files and data between 200+ format pairs such as JSON, CSV, XML, YAML, PDF, Excel and DOCX.
- What you can do
- Convert data and documents between formats, covering pairs among JSON, CSV, XML, YAML, PDF, Excel, DOCX and more.
- Handle structured-data conversions such as JSON to CSV or XML to YAML.
- Handle document conversions involving PDF, Excel and DOCX files.
- No individual tools are listed in the manifest, so the exact operations are not documented.
- When to use it
- Useful when an assistant needs to turn data or documents from one format into another, for example reshaping JSON into CSV or extracting content from a PDF or DOCX into a structured format, without installing local conversion software.
- Requirements
- A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so the user must sign in with the provider's account flow before use. Network access to the hosted endpoint is required.
Installation
In SourceWeft
- Open MCP Data Converter in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.igormilovanovic%2Fdata-converter/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"data-converter": {
"type": "http",
"url": "https://mcp-converter.tnkng.com/mcp"
}
}
}Tools
0Version history
1- v1.4.3LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.