Mellos Mapping
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, 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 (what Claude Code sets for plugin MCP servers), then the server process's own working directory. | |
| MELLOS_MAPPING_TMUX_SOCKET | No | Absolute tmux socket path, for example `/tmp/my-tmux/socket`. Set when using a custom tmux socket; restart the MCP server after changing it. | |
| MELLOS_MAPPING_TMUX_TARGET | No | Explicit tmux session or pane to use for the map pane, such as `work:2.1` or `%7`. Set for multiple attached tmux sessions; restart the MCP 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
ResponsivenessNo issues