MCP server for self-hosted Laserfiche repositories — search and read documents from Claude.
Runs on your machine from its package; the steps are below.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
uvx laserfiche-mcp
MCP client config
{
"mcpServers": {
"laserfiche": {
"command": "uvx",
"args": [
"laserfiche-mcp"
]
}
}
}Owned by the General Conference of Seventh-day Adventists. Not affiliated with or endorsed by Laserfiche.
Let Claude (Desktop, Code, or any MCP
client) search and read documents in a self-hosted
Laserfiche repository — and, if you opt in,
change them. The same program is also a command-line tool (ls, cat,
search, dedupe, ...) for work that needs no AI at all.
Read-only by default. Writes are off until you set LF_READ_ONLY=false,
and destructive actions always need a second confirmation step.
Current release: v2.6.2 — see the CHANGELOG.
uv tool install laserfiche-mcp # or run ad hoc: uvx laserfiche-mcp
laserfiche-mcp setup # asks for your server + account, then tests the connection
laserfiche-mcp ls 1 # list the repository root
Then connect it to Claude. Prefer no terminal? Use the Claude Desktop extension. New to MCP? Read the step-by-step guide (~7 min). Want ready-made prompts and commands? See examples.
Once connected, you can ask Claude things like:
Behind that, it can:
Find things
laserfiche-mcp[images] adds downscaling.Read things
.msg need pip install 'laserfiche-mcp[office]')
— with page ranges for long documents.Analyze
Make changes (opt-in)
Run where you need it
--json output for scripts. See docs/cli.md.Every tool, with details: docs/tools.md.
No terminal, no config files.
Download the extension (needs Claude Desktop).
Double-click it, click Install, and fill in the form:
| Field | What to enter |
|---|---|
| Repository API URL | Your server address, e.g. https://your-server/LFRepositoryAPI |
| Repository name | The repository you pick when signing in to Laserfiche Web Access |
| Username / Password | An account that can read the repository (the password goes in your OS keychain) |
Not sure what to enter? Ask whoever runs Laserfiche at your organization.
Ask Claude something, like "Find every invoice from March in the Accounting folder."
More detail: docs/desktop-extension.md.
uvx laserfiche-mcp # run directly, no install
pip install laserfiche-mcp # or add it to your environment
Needs Python 3.10+ and a reachable Laserfiche Repository API Server with an account that can read it.
Run laserfiche-mcp setup, or set these environment variables:
| Variable | Example | Notes |
|---|---|---|
LF_REPO_API_URL | https://lf.example.com/LFRepositoryAPI | Your Repository API Server |
LF_REPOSITORY_ID | my-repo | |
LF_API_VERSION | v1 (default) or v2 | Wrong value → 400 UnsupportedApiVersion. Probe with curl {LF_REPO_API_URL}/v1/Repositories and /v2/Repositories; the one that returns a repo list is yours. |
LF_USERNAME / LF_PASSWORD | A service account | |
LF_AUTH_MODE | password | |
LF_READ_ONLY | true (default) | false turns on the write tools |
Everything else — write guardrails, size limits, search tuning, web-client links, logging — is in docs/configuration.md.
Warning
Laserfiche Cloud support is beta and has never been verified against a live tenant. If you have Cloud access, please open an issue with what worked or broke. Details in docs/configuration.md.
Claude Code
claude mcp add laserfiche -- uvx laserfiche-mcp
Pass settings with --env LF_REPO_API_URL=... flags, or export them in your shell first.
Claude Desktop — add this to claude_desktop_config.json
(%APPDATA%\Claude\ on Windows, ~/Library/Application Support/Claude/ on macOS), then restart:
{
"mcpServers": {
"laserfiche": {
"command": "uvx",
"args": ["laserfiche-mcp"],
"env": {
"LF_REPO_API_URL": "https://lf.example.com/LFRepositoryAPI",
"LF_REPOSITORY_ID": "my-repo",
"LF_API_VERSION": "v1",
"LF_USERNAME": "service-account",
"LF_PASSWORD": "replace-me",
"LF_AUTH_MODE": "password",
"LF_READ_ONLY": "true"
}
}
}
}
Try a tool without Claude using the MCP Inspector:
npx @modelcontextprotocol/inspector uvx laserfiche-mcp
By default the server talks over stdio to a local client. Web connectors can't launch a local program, so run it as an HTTP server instead:
laserfiche-mcp --http # serves http://127.0.0.1:8000/mcp
For anything beyond your own machine you need TLS, authentication (per-user OAuth or a shared token) and a network path to your Laserfiche server. Setup and the security checklist: docs/remote-http.md.
laserfiche-mcp ls '\HR\Leases' # list a folder (by path or entry ID)
laserfiche-mcp get 4821 --to ./lease.pdf # download a document
laserfiche-mcp cat 4821 --pages 4-9 # print its text
laserfiche-mcp search 'unpaid balance' # full-text search with excerpts
laserfiche-mcp manifest 1 --out inventory.csv # inventory a folder tree
laserfiche-mcp dedupe 1 # find byte-identical documents
Every command takes --json. More recipes in examples;
the full reference is docs/cli.md.
LF_WRITE_PATHS_ALLOW),
limit which write tools exist (LF_WRITE_TOOLS_ALLOWED), and cap folder
deletes.delete, rename and move return a preview and a short-lived token;
nothing changes until the call is repeated with that token.Where your document content goes: Data handling & privacy. All guardrails: docs/safety.md.
Start with one command — it tests your login, probes your server, and tells you what's wrong:
laserfiche-mcp diagnose
| Symptom | Likely cause | Fix |
|---|---|---|
diagnose says UNREACHABLE | Wrong URL, VPN down, or an https:// server whose certificate comes from your internal CA | Fix the URL; for an internal CA set LF_USE_SYSTEM_CA=true (or LF_CA_BUNDLE=<pem>) — not LF_VERIFY_SSL=false, which switches checking off |
CERTIFICATE_VERIFY_FAILED ... hostname mismatch | The URL's host isn't a name on the certificate (e.g. short name vs. the full host.domain name) | Use the host name on the certificate in LF_REPO_API_URL |
diagnose suggests the other API version | LF_API_VERSION mismatch | Use the version it names |
| HTTP 401, or Laserfiche error 9528 | Bad credentials (9528's "LFDS unreachable" wording is misleading) | Re-run laserfiche-mcp setup |
| A setting seems ignored | A misspelled LF_* name — unknown names are silently skipped | diagnose lists any LF_* variable it doesn't recognize |
On Windows, put repository paths in double quotes: laserfiche-mcp list "\HR\Leases".
Claude Desktop logs: %APPDATA%\Claude\logs\ (macOS: ~/Library/Logs/Claude/).
When a tool fails it returns a structured error (not a crash) that tells the model whether to retry, ask you, or give up. See docs/error-contract.md.
| Getting started | Slower walkthrough for people new to MCP |
| Examples | Prompts, commands and config you can copy |
| Configuration | Every LF_* setting |
| Tools | All tools and how to use them |
| Command line | CLI conventions, formats and cost savings |
| Safety model | Write guardrails and confirmation tokens |
| Data handling & privacy | What Claude sees and where data goes |
| Remote HTTP | Web clients, OAuth, per-user access |
| Error contract | Error kinds and codes |
LF_AUTH_MODE=oauth_passthrough runs Laserfiche calls as each user instead of a shared account; needs confirming against a live LFDS tenant (details).get_entry, ...); only laserfiche_{resource}_{verb} remain.Issues, suggestions, and PRs are encouraged and appreciated. Run the tests with:
uv sync --extra dev
uv run pytest && uv run ruff check src tests && uv run mypy src
See CONTRIBUTING.md for setup, where help is most wanted, and the opt-in integration tests. This project is not affiliated with or endorsed by Laserfiche.
This is an open-source project owned by the General Conference of Seventh-day Adventists and available to the public as-is, without warranty. It was created by, and is maintained by, Samuel Hernandez on the General Conference's behalf; the maintainer holds no copyright in it. See the LICENSE file for the full terms.
Bug reports, questions, and suggestions are encouraged and appreciated — please open an issue.