Excel To JSON MCP By WTSolutions

Created By
WTSolutionsa year ago
The Excel to JSON MCP (Model Context Protocol) provides a standardized interface for converting Excel and CSV data into JSON format using the Model Context Protocol. This MCP implementation offers two specific tools for data conversion: excel_to_json_mcp_from_data: Converts tab-separated or comma-separated text data excel_to_json_mcp_from_url: Converts Excel from a provided URL
Overview

What is Excel to JSON MCP?

Excel to JSON MCP is a tool that provides a standardized interface for converting Excel and CSV data into JSON format using the Model Context Protocol (MCP).

How to use Excel to JSON MCP?

Users can utilize two main tools:

  1. excel_to_json_mcp_from_data: For converting tab-separated or comma-separated text data.
  2. excel_to_json_mcp_from_url: For converting Excel files from a provided URL.

Key features of Excel to JSON MCP?

  • Converts Excel and CSV data into JSON format.
  • Supports both direct data input and URL-based file conversion.
  • Automatically detects and converts various data types (numbers, booleans, dates, strings).

Use cases of Excel to JSON MCP?

  1. Transforming Excel spreadsheets into JSON for web applications.
  2. Converting CSV files into JSON for data processing.
  3. Facilitating data interchange between different systems that utilize JSON format.

FAQ from Excel to JSON MCP?

  • Is there a cost to use this tool?

Currently, it is free to use.

  • What formats does it support?

It supports Excel (.xlsx) and CSV formats.

  • What happens if there is an error during conversion?

The API provides descriptive error messages for common issues.

Server Config

{
  "mcpServers": {
    "excel_to_json_by_WTSolutions": {
      "args": [
        "mcp-remote",
        "https://mcp.wtsolutions.cn/excel-to-json-mcp-sse"
      ],
      "command": "npx",
      "tools": [
        "excel_to_json_mcp_from_data",
        "excel_to_json_mcp_from_url"
      ]
    }
  }
}
Project Info
Hosted
Created At
a year ago
Updated At
a year ago
Author Name
WTSolutions
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago