The omni-tool plugin for Claude Code

omni-tool is a Claude Code plugin that connects Claude to the Gala MCP server and adds a teaching layer on top of it. It is published in the gala-chain plugin marketplace, a GitHub repository (aschulergala/claude-plugin-marketplace) that is separate from this package and versioned on its own. This page describes what the plugin does and how it relates to the server; the plugin's own repository is the authority for what a given plugin release contains.

Install

Inside Claude Code, add the marketplace once, then install the plugin:

/plugin marketplace add aschulergala/claude-plugin-marketplace
/plugin install omni-tool

The same from a terminal:

claude plugin marketplace add aschulergala/claude-plugin-marketplace
claude plugin install omni-tool@gala-chain

Restart Claude Code afterwards so the server process starts with the plugin's environment. Then run /omni-tool:setup.

What it ships

Part	What it does
MCP server entry	Starts `@gala-chain/gala-mcp-server` from a release-candidate range of the `1.x` line, with `ENVIRONMENT=prod` and no signing key. All toolsets are loaded: 324 tools and 286 prompts.
Agent `galachain-builder`	A teaching and implementation partner for GalaChain applications. At session start it checks that the server answers and, if not, stops calling tools and shows the setup entry.
Command `/omni-tool:setup`	Checks the server connection, explains `prod` versus `stage` and read-only versus signing, and saves teaching preferences (personality, code style, automatic explanations).
Command `/omni-tool:ask`	Asks a question about GalaChain and answers it from the server's documented SDK examples.
Command `/omni-tool:topics`	Lists the learning topics the server can explain.
Skill `learning-galachain`	The workflow behind a lesson: concept, use case, steps, a current SDK example with the tools that match it, parameters, pitfalls and next topics.
Hook on `gala_launchpad_*` results	After a tool call, if the result says the server is missing, stops further calls and points to `/omni-tool:setup`. For other errors it looks up the matching topic.

The topics come from the server's gala_launchpad_explain_sdk_usage tool, which has 68 topics in this version. The plugin keeps a local index of them for /omni-tool:topics; the server's own list is authoritative when they differ.

The two smaller plugins

The same marketplace also carries two plugins that run the same server with a toolset selection and nothing else, for a smaller tool surface:

Plugin	Toolsets	Tools
`launchpad`	`core`, `launchpad`	289
`swap`	`core`, `gswap`	79

Install either one with /plugin install launchpad or /plugin install swap. They carry no agent, commands or skill. Install one plugin of the three, not several: each starts its own copy of the server, and the model then sees every tool twice.

How it relates to the MCP server

The plugin is the server plus a teaching layer. It does not change what a tool does: every tool call goes through the same server, the same address rules and the same session wallet as in any other client. If you already configured the server yourself (for example with claude mcp add), installing the plugin starts a second server with the same tools. Keep one of them: remove yours with claude mcp remove gala, or do not install the plugin. To change the plugin's environment or toolsets, edit its server entry in your Claude Code configuration as /omni-tool:setup shows, or use the server directly with MCP server setup.

Safety model

Read-only until you add a key. The plugin starts the server with no PRIVATE_KEY, so every read works and every write answers that it needs a wallet. A teaching preference such as "full-access" is a preference of the assistant, not a permission: only a key in the server's environment lets it sign.
prod is the default. With no ENVIRONMENT the server uses the real GalaChain network, and a signed write there moves real assets. Choose stage (the test network) while you learn; the only accepted values are prod and stage.
Quote before you write. Every write has a read counterpart that returns what it would do. The assistant should call it first and show you the result, and you should read it:

gala_launchpad_get_swap_quote_exact_input({
  fromToken: 'GALA|Unit|none|none',
  toToken: 'GUSDC|Unit|none|none',
  amount: '100'
})

gala_launchpad_calculate_buy_amount({
  tokenName: 'anime',
  amount: '100',
  type: 'native'
})

Keys stay out of the conversation. Never paste a private key into a chat, a command or a file the assistant can read; configure it in the server's environment. See security and keys.
The preferences file holds no secrets. /omni-tool:setup writes presentation preferences to .claude/galachain-omnitool.local.md and nothing that reaches the server.

Updating

Update the plugin from its marketplace (/plugin marketplace update gala-chain, then claude plugin update omni-tool@gala-chain). The server it starts is fetched by npx on its own schedule, so the tools you have can be newer than the plugin's own documentation of them: trust the live tool list and gala_launchpad_explain_sdk_usage over any static description, including this page.

Install​

What it ships​

The two smaller plugins​

How it relates to the MCP server​

Safety model​

Updating​