S3eidat Tools MCP Server

S3eidat Tools MCP

The free, private S3eidat Tools as tools your AI assistant can use. PDF, images, text, developer chores, calculators, QR codes and document makers, served by a local MCP server. It runs on your own machine: your files are never uploaded anywhere, there is no account, no API key and no telemetry.

Works with Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex, Gemini CLI and any other MCP client.

npx -y s3eidat-tools-mcp

Docs site: https://s3eidat.github.io/s3eidat-tools-mcp/ · Tool reference: docs/tools.md · Skill: skills/

What you can ask

• "Merge these three PDFs, compress the result and add page numbers."
• "Turn every photo in ~/Desktop/receipts into one PDF."
• "Resize this image to 1200 px wide as WebP and strip the GPS data."
• "Format this JSON and convert it to YAML." · "What does this cron expression mean?"
• "Monthly payment on a 250,000 loan at 5.2% over 25 years?" · "Prayer times in Amman tomorrow."
• "Make a QR code for my Wi-Fi." · "Make an invoice PDF for these items."

Install

You need Node.js 20.19 or newer (22+ recommended). The first run downloads the package; later runs start instantly.

Claude Code

claude mcp add s3eidat -s user -- npx -y s3eidat-tools-mcp

Claude Desktop

One click: download the .mcpb file for your computer from the latest release and double-click it (or drag it into Settings → Extensions). It includes everything, so you don't even need Node.js. You can pick an allowed folder and an output folder in the extension's settings.

Or by hand: Settings → Developer → Edit Config, then add to claude_desktop_config.json and restart Claude:

{
  "mcpServers": {
    "s3eidat": {
      "command": "npx",
      "args": ["-y", "s3eidat-tools-mcp"]
    }
  }
}

On Windows, if Claude can't find npx, use "command": "cmd" and "args": ["/c", "npx", "-y", "s3eidat-tools-mcp"].

Cursor

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "s3eidat": { "command": "npx", "args": ["-y", "s3eidat-tools-mcp"] }
  }
}

VS Code (Copilot agent mode)

code --add-mcp '{"name":"s3eidat","command":"npx","args":["-y","s3eidat-tools-mcp"]}'

or .vscode/mcp.json in a workspace:

{
  "servers": {
    "s3eidat": { "type": "stdio", "command": "npx", "args": ["-y", "s3eidat-tools-mcp"] }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "s3eidat": { "command": "npx", "args": ["-y", "s3eidat-tools-mcp"] }
  }
}

Codex CLI

codex mcp add s3eidat -- npx -y s3eidat-tools-mcp

Gemini CLI

~/.gemini/settings.json:

{
  "mcpServers": {
    "s3eidat": { "command": "npx", "args": ["-y", "s3eidat-tools-mcp"] }
  }
}

Any other client (Streamable HTTP)

npx -y s3eidat-tools-mcp --http --port 8787

Then point the client at http://127.0.0.1:8787/mcp. It only listens on your own machine unless you pass --host. Hosted chat apps (ChatGPT, claude.ai) can only reach servers on the public internet; exposing this server there would expose your files, so use a desktop/CLI client instead.

Options

Example: "args": ["-y", "s3eidat-tools-mcp", "--root", "/Users/me/Documents"].

Many tools, small context?

The full list is about 140 tools, roughly 65k tokens of tool definitions. Clients with tool search (Claude Code) handle that well. If your client has a tool limit (Cursor, Windsurf) or you use a small model, either pick groups (--groups pdf,image is about 17k tokens) or use --compact (about 600 tokens): the model then searches for a tool, reads its inputs and runs it through three meta-tools.

{ "mcpServers": { "s3eidat": { "command": "npx", "args": ["-y", "s3eidat-tools-mcp", "--compact"] } } }

How files work

• Inputs take a local path (absolute, ~/…, or relative to --root) or base64 (raw, base64:…, or a data: URI).
• Outputs are written to the output you give (a file path, or a folder ending in /), or to the output folder. Results return the path and small metadata, not big base64 blobs (set returnBase64 where offered if you need the bytes).
• Chain tools by passing one result's path to the next tool: pdf_from_images → pdf_compress → pdf_page_numbers.

Tools

162 tools. Full reference: docs/tools.md.

Every tool's description links the matching web tool on https://s3eidat.github.io for people who prefer a visual version.

The skill

skills/s3eidat-tools teaches an AI which tool fits which job, how to chain them and when to send a person to the web tool instead. Install steps: skills/README.md.

Privacy

Everything runs locally in the Node process on your machine. The website ports make no network requests at all. A few tools in the "For AI agents" group (such as fetching a web page as Markdown) do use the network; they are marked with openWorldHint so your client can ask before running them. No analytics, no telemetry, no accounts.

Support

The tools are free. If they save you time, buy me a coffee ☕. Want an AI that reads your PDFs, writes and translates? Try s3eidatGPT.

Development

npm ci
npm test          # builds, runs known-answer tests for every tool and an MCP round trip
npm run docs      # regenerates docs/tools.md, docs/*.html, docs/llms.txt
npm run smoke     # drives the built server over MCP stdio
npm run mcpb      # builds a Claude Desktop extension for this platform into mcpb/out/
node dist/index.js --list
npx @modelcontextprotocol/inspector node dist/index.js

Adding a tool: one file in src/tools/<group>/…/<slug>.ts whose default export is defineTool({...}) from src/registry.ts (the contract is documented at the top of that file). It is discovered automatically. Add a known-answer test in test/. Releasing: RELEASING.md.

License

MIT © Omar (s3eidat)