Skip to main content
Glama
enesjakozh
ArchimedesCrypto

MCP Excel Reader

by ArchimedesCrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

MCP 엑셀 리더

대장간 배지 자동 청킹 및 페이지 매김 기능을 지원하는 Excel 파일을 읽기 위한 모델 컨텍스트 프로토콜(MCP) 서버입니다. SheetJS와 TypeScript로 구축된 이 도구는 대용량 Excel 파일을 관리하기 쉬운 청크로 자동 분할하여 효율적으로 처리할 수 있도록 도와줍니다.

특징

  • 📊 자동 크기 제한으로 Excel 파일(.xlsx, .xls) 읽기

  • 🔄 대용량 데이터 세트에 대한 자동 청킹

  • 📑 시트 선택 및 행 페이지 매김

  • 📅 적절한 날짜 처리

  • ⚡ 대용량 파일에 최적화됨

  • 🛡️ 오류 처리 및 검증

Related MCP server: Excel MCP Server

설치

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 Excel Reader를 자동으로 설치하려면:

지엑스피1

MCP 서버로서

  1. 전역적으로 설치:

npm install -g @archimdescrypto/excel-reader

  1. MCP 설정 파일에 다음을 추가합니다(일반적으로 ~/.config/claude/settings.json 또는 이와 동등한 파일).

{
  "mcpServers": {
    "excel-reader": {
      "command": "excel-reader",
      "env": {}
    }
  }
}

개발을 위해

  1. 저장소를 복제합니다.

git clone https://github.com/ArchimdesCrypto/mcp-excel-reader.git
cd mcp-excel-reader

  1. 종속성 설치:

npm install

  1. 프로젝트를 빌드하세요:

npm run build

용법

용법

Excel Reader는 다음 매개변수를 포함하는 단일 도구인 read_excel 제공합니다.

interface ReadExcelArgs {
  filePath: string;      // Path to Excel file
  sheetName?: string;    // Optional sheet name (defaults to first sheet)
  startRow?: number;     // Optional starting row for pagination
  maxRows?: number;      // Optional maximum rows to read
}

// Response format
interface ExcelResponse {
  fileName: string;
  totalSheets: number;
  currentSheet: {
    name: string;
    totalRows: number;
    totalColumns: number;
    chunk: {
      rowStart: number;
      rowEnd: number;
      columns: string[];
      data: Record<string, any>[];
    };
    hasMore: boolean;
    nextChunk?: {
      rowStart: number;
      columns: string[];
    };
  };
}

기본 사용법

Claude 또는 다른 MCP 호환 AI와 함께 사용하는 경우:

Read the Excel file at path/to/file.xlsx

AI는 이 도구를 사용하여 파일을 읽고 큰 파일의 청킹을 자동으로 처리합니다.

특징

  1. 자동 청킹

    • 대용량 파일을 관리하기 쉬운 청크로 자동 분할합니다.

    • 기본 청크 크기는 100KB입니다.

    • 페이지 매김을 위한 메타데이터를 제공합니다

  2. 시트 선택

    • 이름으로 특정 시트 읽기

    • 지정하지 않으면 첫 번째 시트로 기본 설정됩니다.

  3. 행 페이지 매김

    • startRow 및 maxRows를 사용하여 읽을 행을 제어합니다.

    • 연속 읽기를 위한 다음 청크 정보 가져오기

  4. 오류 처리

    • 파일 존재 여부와 형식을 검증합니다.

    • 명확한 오류 메시지를 제공합니다

    • 잘못된 Excel 파일을 정상적으로 처리합니다.

SheetJS 기능으로 확장하기

Excel Reader는 SheetJS 기반으로 구축되었으며 강력한 기능으로 확장할 수 있습니다.

사용 가능한 확장 프로그램

  1. 수식 처리

    // Enable formula parsing
const wb = XLSX.read(data, {
  cellFormula: true,
  cellNF: true
});

  2. 셀 서식

    // Access cell styles and formatting
const styles = Object.keys(worksheet)
  .filter(key => key[0] !== '!')
  .map(key => ({
    cell: key,
    style: worksheet[key].s
  }));

  3. 데이터 검증

    // Access data validation rules
const validation = worksheet['!dataValidation'];

  4. 시트 특징

    • 병합된 셀: worksheet['!merges']

    • 숨겨진 행/열: worksheet['!rows'] , worksheet['!cols']

    • 시트 보호: worksheet['!protect']

더 많은 기능과 자세한 설명서를 보려면 SheetJS 설명서를 방문하세요.

기여하다

  1. 저장소를 포크하세요

  2. 기능 브랜치를 생성합니다( git checkout -b feature/amazing-feature )

  3. 변경 사항을 커밋하세요( git commit -m 'Add some amazing feature' )

  4. 브랜치에 푸시( git push origin feature/amazing-feature )

  5. 풀 리퀘스트 열기

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 라이선스 파일을 참조하세요.

감사의 말

Available Tools

1 tool
read_excelB

Read an Excel file and return its contents as structured data

ParametersJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the Excel file to read
sheetNameNoName of the sheet to read (optional)
startRowNoStarting row index (optional)
maxRowsNoMaximum number of rows to read (optional)

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions reading and returning data, implying a read-only operation, but fails to address critical aspects like error handling (e.g., what happens if the file doesn't exist or is corrupted), performance considerations, or format specifics of the returned structured data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded with the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits and output format, which are important for a data-reading tool without structured output documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the input schema already documents all parameters thoroughly. The description adds no additional meaning beyond what the schema provides, such as examples or usage tips for the parameters, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Read') and resource ('an Excel file') with the outcome ('return its contents as structured data'). It's specific about what the tool does, but since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It simply states what the tool does without context for usage decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedread_excel
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'read_excel' has a clear and distinct purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The single tool name 'read_excel' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.

Tool Count2/5

A single tool is generally too few for a server named 'MCP Excel Reader', as it suggests a limited scope that may not support typical Excel-related workflows like writing, updating, or querying data. This feels thin for the apparent domain.

Completeness2/5

The tool surface is severely incomplete for an Excel reader domain. While reading is covered, there are significant gaps such as writing, editing, formatting, or analyzing Excel files, which will likely cause agent failures in broader tasks.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

  • ExcelReadMCP

    OgumaruSuisan
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables reading and searching Excel files through MCP-compatible clients. Provides tools to retrieve workbook metadata, read sheet contents, and search across all sheets using absolute file paths.
    1
    MIT

  • xls-mcp-servers

    Lincyghb
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for reading and writing .xls (Excel 97-2003) files, enabling data manipulation, sheet listing, and metadata retrieval.
    MIT

  • excel-tools-mcp

    Hcshenziyang
    A
    license
    A
    quality
    C
    maintenance
    MCP server for reading and inspecting local Excel files (.xlsx, .xlsm, .xls, .xlsb, .ods) with tools for inspecting metadata, reading ranges, and profiling structure.
    3
    5 npm
    MIT

Appeared in Searches