Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-excel-reader Show me the first rows of /data/report.xlsx"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server untuk baca file Excel (.xlsx, .xls). Gratis, open source, tanpa API key.
Baca file Excel (.xlsx, .xls)
Tampilkan jumlah baris & kolom
Tampilkan nama-nama kolom
Tampilkan 5 baris pertama sebagai preview
Error handling yang clean
Related MCP server: Excel Explorer
git clone https://github.com/username/mcp-excel-reader.git
cd mcp-excel-reader
npm install
npm run buildnpm startnpx @modelcontextprotocol/inspectorBuka browser ke http://localhost:6274, lalu connect:
Command: node
Arguments: dist/server.js
Working Directory: /path/to/mcp-excel-gratis
Tambahkan di claude_desktop_config.json:
{
"mcpServers": {
"mcp-excel-gratis": {
"command": "node",
"args": ["/path/to/mcp-excel-gratis/dist/server.js"]
}
}
}read_excelInput:
Parameter | Type | Description |
| string | Path lengkap ke file Excel |
Output:
{
"filePath": "/path/to/file.xlsx",
"sheetName": "Sheet1",
"rowCount": 100,
"columnCount": 5,
"columnNames": ["Name", "Email", "Phone", "City", "Value"],
"firstFiveRows": [
{
"Name": "John Doe",
"Email": "john@example.com",
"Phone": "08123456789",
"City": "Jakarta",
"Value": 1500000
}
]
}The MCP server successfully reads Excel workbook data through the read_excel tool.
TypeScript
MIT
| Name | Required | Description | Default |
|---|---|---|---|
| filePath | Yes | Absolute path to the Excel file (.xlsx, .xls) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0read_excelScored across 1 tool
With only one tool, there is no potential for confusion between tools. The name 'read_excel' clearly indicates its purpose, making it unambiguous.
The single tool follows a clear verb_noun naming pattern (read_excel), and there are no other tools to introduce inconsistency.
Having only one tool is too few for an Excel reader, which typically needs operations like listing sheets, reading specific ranges, or fetching metadata. This feels thin for the server's stated purpose.
The server only offers a single 'read_excel' operation, leaving gaps for specifying sheets, ranges, or handling different data formats. This is a significant limitation for a comprehensive Excel reading experience.
The Excel engine for AI agents: read, check and edit Excel models over MCP.
Convert Apple Numbers (.numbers) to Excel (.xlsx) in the browser — first sheet free. MCP v1.1.0 (Streamable HTTP) exposes four tools: open_numbers2excel (open site / Stripe checkout intents; conversion is browser-local), get_site_info (product overview, pricing, URLs; read-only), get_pro_status (Stripe subscription_id sub_… status), get_unlock_from_session (Checkout session_id cs_… → entitlement). Path A: MCP does not accept or upload files.
ParseHub.dev is a hosted document-to-records service with a remote MCP server. Agents can upload a CSV, PDF, or Word file, summarize and analyze CSV data (filter, sort, group_by, and more), read text from PDF and Word files, extract attendees, agenda items, and action items from meeting notes, ask a question about an uploaded document, and store files as database records to list and read later. Each account sees only its own files and records. **Endpoint:** `https://parsehub.dev/mcp` (Streamable HTTP, stateless) **Auth:** API key in the `X-API-Key` header (keys start with `mcp_`), or `Authorization: Bearer <API key or JWT>`. Every request without credentials returns 401. **Plans:** Free (100 API requests/month, 1 document upload), or 5,000 requests/month on the $9/month or $42/year plan. Every MCP request counts toward the allowance. **Tools:** upload_csv, summarize_csv, analyze_csv, upload_document, read_document, extract_meeting_notes, ask_document, database_status, list_database_documents, get_database_document, store_document, extract_stored_meeting_notes, export_database (administrators only). Not affiliated with ParseHub (parsehub.com), the web-scraping tool. ParseHub.dev does not scrape websites. By Poietes LLC. Docs: https://parsehub.dev/guide#connect-via-mcp
Query, join, profile, clean and convert CSV/JSON/Parquet with server-side DuckDB over MCP.
