analyze_barcode — ODDWOOD Barcode Tool MCP Tool
analyze_barcode
(analyze barcode) is one of 2 tools on the
ODDWOOD Barcode Tool
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_barcode from your client
- Claude Code ODDWOOD Barcode Tool analyze_barcode run in your project directory
- Claude Desktop ODDWOOD Barcode Tool analyze_barcode ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ODDWOOD Barcode Tool analyze_barcode ~/.cursor/mcp.json
- VS Code ODDWOOD Barcode Tool analyze_barcode .vscode/mcp.json
- Zed ODDWOOD Barcode Tool analyze_barcode ~/.config/zed/settings.json
- Windsurf ODDWOOD Barcode Tool analyze_barcode ~/.codeium/windsurf/mcp_config.json
- Cline ODDWOOD Barcode Tool analyze_barcode ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ODDWOOD Barcode Tool analyze_barcode ~/.gemini/settings.json
- Grok ODDWOOD Barcode Tool analyze_barcode .mcp.json (in your project root)
- ChatGPT ODDWOOD Barcode Tool analyze_barcode Settings → Connectors → Advanced → Developer mode
- Claude.ai ODDWOOD Barcode Tool analyze_barcode Settings → Connectors → Add custom connector
- LangChain ODDWOOD Barcode Tool analyze_barcode pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http barcode-tool https://barcode-tool.fly.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 October 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.