ReNile-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind. | 0.0.0.0 |
| PORT | No | Port to bind. | 8000 |
| LOG_LEVEL | No | Logging level. | INFO |
| ALLOWED_HOSTS | No | Comma-separated. Must include the public hostname or requests are rejected with 421. Each entry also matches that host on any port. | |
| STATELESS_HTTP | No | Whether to run stateless HTTP. See 'Scaling'. | false |
| ALLOWED_ORIGINS | No | Comma-separated. | |
| HTTP_MAX_ATTEMPTS | No | Total attempts per request; 1 disables retrying. Timeouts are never retried. | 2 |
| RENILE_ISSUER_URL | Yes | Required. The ReNile authorization server. No trailing slash. | |
| RENILE_API_BASE_URL | No | Base URL for ReNile API. | https://renile-iot.com |
| RENILE_DEVICES_PATH | No | Path for devices endpoint. | /api/v1/devices/names/ |
| STALE_AFTER_SECONDS | No | Age past which a reading is flagged is_stale. | 3600 |
| HTTP_MAX_CONNECTIONS | No | Shared upstream pool size. | 100 |
| HTTP_TIMEOUT_SECONDS | No | Timeout in seconds for upstream HTTP requests. | 15.0 |
| RENILE_SNAPSHOT_PATH | No | Path for snapshot endpoint. | /api/v1/snapshot/ |
| ERROR_BODY_PREVIEW_CHARS | No | How much of an upstream error body to quote back. | 200 |
| RENILE_RESOURCE_SERVER_URL | Yes | Required. The exact public URL clients use, including /mcp. | |
| RENILE_UPSTREAM_AUTH_SCHEME | No | Scheme used when forwarding the token upstream. The platform uses JWT, not Bearer. | JWT |
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/mohamedelsayadrenile/IOT-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server