Local Commerce Bridge Setup — Wisely x402 Agent-Payment Infrastructure MCP Resource
Local Commerce Bridge Setup
is one of 8 resources on the
Wisely x402 Agent-Payment Infrastructure
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Local Commerce Bridge Setup from your client
- Claude Code Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup run in your project directory
- Claude Desktop Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup ~/.cursor/mcp.json
- VS Code Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup .vscode/mcp.json
- Zed Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup ~/.config/zed/settings.json
- Windsurf Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup ~/.codeium/windsurf/mcp_config.json
- Cline Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup ~/.gemini/settings.json
- Grok Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup .mcp.json (in your project root)
- ChatGPT Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup Settings → Connectors → Advanced → Developer mode
- Claude.ai Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup Settings → Connectors → Add custom connector
- LangChain Wisely x402 Agent-Payment Infrastructure Resource/Local Commerce Bridge Setup pip install langchain-mcp-adapters
Other resources on this server
Wisely x402 Agent-Payment Infrastructure also offers 6 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.