Skip to main content
Glama
MauricioPerera

subway-mcp-server

by MauricioPerera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
delegate_to_codexA

Runs OpenAI's Codex CLI non-interactively (codex exec) to execute a coding task and returns its final message.

Args:

  • prompt (string, required): task instructions for Codex

  • cwd (string, optional): absolute working directory for the task

  • model (string, optional): model override (e.g. "gpt-5.6-luna")

  • timeout_seconds (number, optional, default 600): kill the process after this many seconds

  • auto_approve (boolean, optional, default false): bypass Codex's shell/edit approval prompts. Without this, tasks that need to run a command or edit a file will fail immediately since there is no terminal to approve from.

Returns structured JSON: { success, final_message, exit_code, timed_out, stderr? }.

Error Handling:

  • success=false with a non-zero exit_code and stderr populated means Codex reported an error (e.g. auth, invalid model, sandbox denial)

  • timed_out=true means the task exceeded timeout_seconds and was killed

delegate_to_claudeA

Runs Claude Code non-interactively (claude -p --output-format json) to execute a task and returns its final message.

Args:

  • prompt (string, required): task instructions for Claude

  • cwd (string, optional): absolute working directory for the task

  • model (string, optional): model override (e.g. "claude-opus-4-8")

  • timeout_seconds (number, optional, default 600): kill the process after this many seconds

  • auto_approve (boolean, optional, default false): bypass Claude's tool-permission prompts (--dangerously-skip-permissions). Without this, tasks that need to use tools will fail immediately since there is no terminal to approve from.

Returns structured JSON: { success, final_message, exit_code, timed_out, stderr? }.

Error Handling:

  • success=false with a non-zero exit_code and stderr populated means the CLI reported an error (e.g. auth, invalid model)

  • timed_out=true means the task exceeded timeout_seconds and was killed

delegate_to_agyA

Runs the Antigravity CLI non-interactively (agy -p) to execute a task and returns its response.

Args:

  • prompt (string, required): task instructions for the agy agent

  • cwd (string, optional): absolute working directory for the task

  • model (string, optional): model override

  • timeout_seconds (number, optional, default 600): kill the process after this many seconds

  • auto_approve (boolean, optional, default false): bypass agy's tool-permission prompts (--dangerously-skip-permissions). Without this, tasks that need to use tools will fail immediately since there is no terminal to approve from.

Returns structured JSON: { success, final_message, exit_code, timed_out, stderr? }. Note: agy has no JSON output mode, so final_message is the raw trimmed stdout.

Error Handling:

  • success=false with a non-zero exit_code and stderr populated means the CLI reported an error

  • timed_out=true means the task exceeded timeout_seconds and was killed

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation2/5

The three tools are nearly identical in description and parameters, differing only in the target CLI. An agent would struggle to choose between them without additional context about each CLI's capabilities.

Naming Consistency5/5

All tools follow the consistent pattern 'delegate_to_<name>', making it clear they are delegation actions to specific CLIs.

Tool Count5/5

Three tools is appropriate for a server focused on delegating to a specific set of AI CLIs. The count is within the typical well-scoped range.

Completeness3/5

The server covers three major AI CLIs, but lacks tools for listing available CLIs, models, or managing runs, which leaves minor gaps for agent workflows.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources