Mellos Mapping
by kazukik24951
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MELLOS_MAPPING_CWD | No | An explicit override for the project directory the server uses, for clients that spawn servers from a fixed directory. The server picks its project directory in this order: MELLOS_MAPPING_CWD, then CLAUDE_PROJECT_DIR, then the server process's own working directory. Set it when your client would otherwise start the server somewhere other than the project you are working in. The map file lands in this directory (.mellos/map.json). | |
| MELLOS_MAPPING_TMUX_SOCKET | No | Absolute tmux socket path, for example '/tmp/my-tmux/socket', used on Linux and macOS for multiple attached sessions or a custom tmux socket. Set this in the environment of the MCP server; restart the server after changing it. | |
| MELLOS_MAPPING_TMUX_TARGET | No | Explicit tmux session or pane to use for the map pane on Linux and macOS, such as 'work:2.1' or '%7'. Set this in the environment of the MCP server for multiple attached sessions or a custom tmux socket; restart the server after changing it. |
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 | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessResponsive