About mcp-file-processor
mcp-file-processor is a local MCP server for extracting and preparing text from documents and code for RAG pipelines. It combines format handling with keyword extraction, content detection, and configurable chunking.
Key features
- 01Extract text from documents and code
- 02Extract ranked keywords
- 03Detect code and natural language
- 04Split text into overlapping chunks
- 05Process files in one operation
Use cases
- 01Prepare PDFs and office files for RAG
- 02Chunk text for embedding pipelines
- 03Identify programming language in file content
MCP support
It exposes file-processing tools and a supported-types resource to MCP clients. The server runs locally and needs no API keys.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
6Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| content | string | Yes | File content — base64-encoded for binary formats (PDF, DOCX), raw text for text formats |
| fileType | string | Yes | MIME type (e.g. "application/pdf") or file extension (e.g. ".pdf", "pdf", ".ts") |
Details
From the project README@opafex/mcp-file-processor
MCP server for universal text extraction, keyword extraction, language detection, and text chunking — designed for RAG pipelines.
Supports PDF, DOCX, CSV, JSON, Markdown, HTML, and code files. Zero platform dependencies.
Installation
npm install @opafex/mcp-file-processor
Requires Node.js 20+.
Quick Start
Add to Claude Code / Claude Desktop
{
"mcpServers": {
"file-processor": {
"command": "npx",
"args": ["@opafex/mcp-file-processor"]
}
}
}
No API keys needed — everything runs locally.
Tools
extract_text
Extract text content from a file.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | File content — base64 for binary formats (PDF, DOCX), raw text for text formats |
fileType | string | Yes | MIME type (e.g. "application/pdf") or extension (e.g. ".pdf", "pdf") |
Example response
{
"success": true,
"text": "Extracted text content here...",
"wordCount": 142,
"pageCount": 3,
"processingTimeMs": 45
}
extract_keywords
Extract ranked keywords from text. Filters stop words, sorted by frequency.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text to extract keywords from |
limit | number | No | Max keywords to return (default: 20) |
Example response
{
"success": true,
"keywords": [
{ "word": "javascript", "frequency": 8 },
{ "word": "framework", "frequency": 4 },
{ "word": "react", "frequency": 3 }
],
"totalWords": 156
}
detect_language
Detect whether content is code, natural language, or mixed.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text to analyse |
fileName | string | No | File name for extension-based detection (e.g. "app.ts") |
Example response
{
"success": true,
"contentType": "code",
"programmingLanguage": "typescript"
}
chunk_text
Split text into overlapping chunks for RAG/embedding pipelines.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text to chunk |
chunkSize | number | No | Target chunk size in characters (default: 1000) |
overlap | number | No | Overlap between chunks in characters (default: 200) |
Example response
{
"success": true,
"chunks": [
{ "index": 0, "text": "...", "startOffset": 0, "endOffset": 1000, "wordCount": 167 },
{ "index": 1, "text": "...", "startOffset": 800, "endOffset": 1800, "wordCount": 172 }
],
"totalChunks": 5,
"totalCharacters": 4200
}
process_file
All-in-one: extract text, detect content type, extract keywords, and chunk.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | File content (base64 or raw text) |
fileType | string | Yes | MIME type or file extension |
chunkSize | number | No | Chunk size in characters (default: 1000) |
chunkOverlap | number | No | Overlap in characters (default: 200) |
keywordLimit | number | No | Max keywords (default: 20) |
server_info (built-in)
Returns server metadata, registered tools, and resources.
Resources
| Resource | Description |
|---|---|
file-processor://supported-types | Lists all supported MIME types and file extensions |
Supported Formats
| Format | Extension | Input |
|---|---|---|
.pdf | base64 | |
| Word | .docx, .doc | base64 |
| Plain text | .txt | raw text |
| Markdown | .md | raw text |
| CSV | .csv | raw text |
| JSON | .json | raw text |
| HTML | .html | raw text |
| XML | .xml | raw text |
| JavaScript | .js, .jsx, .mjs | raw text |
| TypeScript | .ts, .tsx | raw text |
| Python | .py | raw text |
| Java | .java | raw text |
| Go | .go | raw text |
| Rust | .rs | raw text |
| C/C++ | .c, .cpp, .h | raw text |
Development
npm run build # Compile TypeScript
npm run dev # Run with tsx
npm test # Run tests
npm start # Run compiled server
Library Usage
import { FileProcessorService } from '@opafex/mcp-file-processor/service';
const service = new FileProcessorService();
const result = await service.processFile(
'Hello world, this is a document.',
'.txt',
500, // chunk size
100 // overlap
);
Contributing
Found a bug or have a feature request? Open an issue.
License
MIT — see LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.