renfield-mcp-filesystem
by ebongard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENFIELD_URL | Yes | Renfield backend base URL | |
| FILES_MCP_HOST | No | MCP server bind host | 0.0.0.0 |
| FILES_MCP_PORT | No | MCP server bind port | 8080 |
| FILES_ROOTS_YAML | No | path to the mounted roots.yaml (reloaded on change) | |
| FILES_SETTLE_SECONDS | No | SMB settle-debounce window | 2.0 |
| RENFIELD_INGEST_TOKEN | Yes | folder-ingest Bearer token | |
| FILES_MAX_FILE_SIZE_MB | No | size ceiling (enforced before push) | 50 |
| FILES_ALLOWED_EXTENSIONS | No | local extension allowlist | pdf,docx,... |
| FILES_NOTIFY_WEBHOOK_URL | No | optional failure/disconnect webhook URL | |
| FILES_NOTIFY_WEBHOOK_TOKEN | No | optional webhook token |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ebongard/renfield-mcp-filesystem'
If you have feedback or need assistance with the MCP directory API, please join our Discord server