Rikune
by Last-emo-boy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLUGINS | No | Controls which plugins are loaded. Use "*" for all built-ins, a comma-separated list for selected plugins, or "-dynamic" to exclude dynamic plugins. Example: PLUGINS=* | |
| NODE_ENV | No | Node.js environment mode, e.g. "production". | production |
| API_ENABLED | No | Whether to enable the embedded HTTP API and dashboard. In MCP client configurations this is often set to "false" to disable the HTTP server (e.g. API_ENABLED=false). | |
| RIKUNE_API_KEY | No | API key used to authenticate to the HTTP API and dashboard. If not supplied, the installer generates a random 32-byte key. The local dashboard is accessible at http://127.0.0.1:18080/?key=<RIKUNE_API_KEY>. | |
| PYTHONUNBUFFERED | No | Ensures Python subprocesses run unbuffered, useful for logging and worker output. | 1 |
| RIKUNE_DATA_ROOT | No | Root directory for persistent data (samples, artifacts, uploads, SQLite database, logs). On WSL2, this must be on the Linux filesystem (e.g. ~/.rikune), not /mnt/c or other DrvFS paths. | ~/.rikune |
| API_PUBLIC_BASE_URL | No | Client-reachable HTTPS base URL for remote analyzer or rikune-agent deployments (e.g. https://analyzer.example.com). Upload sessions then return public upload_url / status_url values instead of container-local localhost URLs. | |
| RIKUNE_ANALYZER_PUBLIC_URL | No | Alternative to API_PUBLIC_BASE_URL for setting the public analyzer URL. | |
| RIKUNE_API_PUBLIC_BASE_URL | No | Alternative to API_PUBLIC_BASE_URL for setting the public base URL of the Rikune API. |
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/Last-emo-boy/rikune'
If you have feedback or need assistance with the MCP directory API, please join our Discord server