agentmods.dev

switch-dc

A command for switching the Catalyst by Zoho MCP server between supported regional data centers.

In plain words
What is it for?
Use it to select a data center such as US, EU, IN, AU, CA, SA, JP, or UAE and update the related settings.
Why use it?
It avoids manually editing several configuration files when changing the server region.

Command

0 20d ago B scan 13 tokens original Apache-2.0
View the source file catalystbyzoho/claude-plugin
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/catalystbyzoho/claude-plugin/switch-dc
Clone the repo
git clone --depth 1 https://github.com/catalystbyzoho/claude-plugin
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 529 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00529
Opus 5 $0.00006 $0.00264
Sonnet 5 $0.00003 $0.00106
Haiku 4.5 $0.00001 $0.00053

Measured 2d ago against content hash 8331b5d86aa6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

switch-dc scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

`find ~/.claude/plugins/cache/catalyst-by-zoho -name ".mcp.json"`
commands/switch-dc.md · 49 lines

What it actually says

Switch the Catalyst by Zoho MCP server to the data center specified in: $ARGUMENTS

Follow these steps exactly:

Step 1 — Resolve the target DC

Valid values: US, EU, IN, AU, CA, SA, JP, UAE (case-insensitive). If $ARGUMENTS is empty or unrecognized, ask the user which DC they want before proceeding.

Map the DC to its MCP URL:

  • US → https://catalyst.zohomcp.com/mcp/message
  • EU → https://catalyst.zohomcp.eu/mcp/message
  • IN → https://catalyst.zohomcp.in/mcp/message
  • AU → https://catalyst.zohomcp.com.au/mcp/message
  • CA → https://catalyst.zohomcp.ca/mcp/message
  • SA → https://catalyst.zohomcp.sa/mcp/message
  • JP → https://catalyst.zohomcp.jp/mcp/message
  • UAE → https://catalyst.zohomcp.ae/mcp/message

Step 2 — Find all config files to update

The plugin URL is cached in multiple locations. Find them all:

  1. Plugin source — read ~/.claude/settings.json, get the path at extraKnownMarketplaces.catalyst-by-zoho.source.path, then open .mcp.json at that path.

  2. Marketplace cache: ~/.claude/plugins/marketplaces/catalyst-by-zoho/.mcp.json

  3. Version cache — run: find ~/.claude/plugins/cache/catalyst-by-zoho -name ".mcp.json" and update every file returned.

Step 3 — Update the URL in every file

In each file, set the url field to the new DC's MCP URL. Do not modify any other fields.

Step 4 — Confirm and instruct the user

Tell the user:

  • Which files were updated and what URL was set.
  • To restart Claude Code for the change to take effect.
  • That after restart, the new DC will prompt for a browser login — this is expected and required.
  • That their existing session on the old DC is not affected.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 49 lines · 13 tokens per session scan B 8331b5d86aa6

Subscribe to this mod's changes

switch-dc is a command published in the GitHub repository catalystbyzoho/claude-plugin (0 stars, last pushed 20d ago), licensed Apache-2.0. It adds 13 tokens to every session and 529 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens