fileee-mcp-server
by strausmann
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILEEE_MODE | No | Fileee mode: 'single' for one account, 'multi' for multiple accounts. | |
| MCP_API_TOKEN | No | Static API token for token auth mode. Required when MCP_AUTH_MODE=token. | |
| MCP_AUTH_MODE | No | Authentication mode: 'token' for static bearer token, 'oidc' for OAuth 2.1 resource server. | |
| FILEEE_ACCOUNTS | No | Comma-separated list of account keys for multi-account mode. | |
| FILEEE_PASSWORD | No | Fileee password for single account mode. | |
| FILEEE_USERNAME | No | Fileee username for single account mode. | |
| MCP_OIDC_ISSUER | No | OIDC issuer URL. | |
| FILEEE_TOTP_SEED | No | TOTP seed for two-factor authentication (optional). | |
| MCP_RESOURCE_URL | No | The public URL of the MCP endpoint. | |
| MCP_OIDC_AUDIENCE | No | OIDC audience (client ID). | |
| FILEEE_CAPABILITIES | No | Comma-separated capability groups: read, write, share, destructive. Default is read. | read |
| MCP_ALLOWED_SUBJECTS | No | Comma-separated list of allowed subjects for single-account OIDC mode. | |
| FILEEE_ALLOW_DESTRUCTIVE | No | Set to 'true' to enable destructive capabilities. | |
| MCP_OIDC_CAPABILITY_CLAIM | No | OIDC claim (e.g., roles, groups) that carries the user's capabilities. Optional. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/strausmann/fileee-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server