giftbit_get_brand — Giftbit MCP by usefulapi MCP Tool
giftbit_get_brand
(giftbit get brand) is one of 14 tools on the
Giftbit MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call giftbit_get_brand from your client
- Claude Code Giftbit MCP by usefulapi giftbit_get_brand run in your project directory
- Claude Desktop Giftbit MCP by usefulapi giftbit_get_brand ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Giftbit MCP by usefulapi giftbit_get_brand ~/.cursor/mcp.json
- VS Code Giftbit MCP by usefulapi giftbit_get_brand .vscode/mcp.json
- Zed Giftbit MCP by usefulapi giftbit_get_brand ~/.config/zed/settings.json
- Windsurf Giftbit MCP by usefulapi giftbit_get_brand ~/.codeium/windsurf/mcp_config.json
- Cline Giftbit MCP by usefulapi giftbit_get_brand ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Giftbit MCP by usefulapi giftbit_get_brand ~/.gemini/settings.json
- Grok Giftbit MCP by usefulapi giftbit_get_brand .mcp.json (in your project root)
- ChatGPT Giftbit MCP by usefulapi giftbit_get_brand Settings → Connectors → Advanced → Developer mode
- Claude.ai Giftbit MCP by usefulapi giftbit_get_brand Settings → Connectors → Add custom connector
- LangChain Giftbit MCP by usefulapi giftbit_get_brand pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http giftbit https://giftbit.usefulapi.io/mcpOther tools on this server
- giftbit_list_brands
- giftbit_list_regions
- giftbit_list_rewards
- giftbit_get_reward
- giftbit_get_order
- giftbit_get_link_urls
- giftbit_get_funds
- giftbit_create_email_reward
- giftbit_create_shortlink_order
- giftbit_create_direct_link_order
- giftbit_create_embedded_reward
- giftbit_resend_reward
- giftbit_cancel_reward
This list was read from the server itself, by connecting to it and calling tools/list on 7 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.