apply_as_supplier — Galactic Bridge: sourcing and delivery to Africa MCP Tool Mutating
apply_as_supplier
(apply as supplier) is one of 9 tools on the
Galactic Bridge: sourcing and delivery to Africa
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call apply_as_supplier from your client
- Claude Code Galactic Bridge: sourcing and delivery to Africa apply_as_supplier run in your project directory
- Claude Desktop Galactic Bridge: sourcing and delivery to Africa apply_as_supplier ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Galactic Bridge: sourcing and delivery to Africa apply_as_supplier ~/.cursor/mcp.json
- VS Code Galactic Bridge: sourcing and delivery to Africa apply_as_supplier .vscode/mcp.json
- Zed Galactic Bridge: sourcing and delivery to Africa apply_as_supplier ~/.config/zed/settings.json
- Windsurf Galactic Bridge: sourcing and delivery to Africa apply_as_supplier ~/.codeium/windsurf/mcp_config.json
- Cline Galactic Bridge: sourcing and delivery to Africa apply_as_supplier ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Galactic Bridge: sourcing and delivery to Africa apply_as_supplier ~/.gemini/settings.json
- Grok Galactic Bridge: sourcing and delivery to Africa apply_as_supplier .mcp.json (in your project root)
- ChatGPT Galactic Bridge: sourcing and delivery to Africa apply_as_supplier Settings → Connectors → Advanced → Developer mode
- Claude.ai Galactic Bridge: sourcing and delivery to Africa apply_as_supplier Settings → Connectors → Add custom connector
- LangChain Galactic Bridge: sourcing and delivery to Africa apply_as_supplier pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sourcing https://galacticbridge.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.