Click on "Install 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. Dates show when Glama detected each change.
v1.0.0read_excelWith 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Query, join, profile, clean and convert CSV/JSON/Parquet with server-side DuckDB over MCP.
Excel analytics: inspect, query (JSON rows), charts, and JSON-to-xlsx workbook writing.
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rayasesan/mcp-excel-reader'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
