marker-watch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKER_WATCH_MCP_CWD | No | Working directory for the command. Defaults to the current directory if not set. | |
| MARKER_WATCH_MCP_ARGS | No | Arguments to pass to the command. Use a JSON-encoded array or space-separated string as appropriate. | |
| MARKER_WATCH_MCP_COMMAND | Yes | The command to run and watch for markers. Equivalent to the first argument after `--`. | |
| MARKER_WATCH_MCP_LOG_FILE | No | Optional path to write a raw output log. | |
| MARKER_WATCH_MCP_END_MARKER | Yes | Literal end marker expected in a complete output line. | |
| MARKER_WATCH_MCP_START_MARKER | Yes | Literal start marker expected in a complete output line. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_build_statusB | Return the build process state and latest completed version. |
| get_buildC | Return the build result of the specified version. |
| await_buildC | Await the build result of the first completed version after afterVersion. |
| start_build_waitC | Start a non-blocking wait for the first completed version after afterVersion. |
| get_build_waitC | Return the state or final result of a non-blocking build wait. |
| debug_get_live_outputA | Return recent raw stdout and stderr from build processes. Meant only for debugging stuck builds. |
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/foxfirecodes/marker-watch-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server