How can we help?
three.ws is an open-source 3D AI agent platform, and home of the x402 MCP server for IBM Granite. Pick the channel that fits — bug reports and feature requests go to GitHub, "how do I…" questions to Discussions, and anything private or account-specific to email. Security reports get their own address.
Get in touch
Every channel below is monitored by the three.ws team.
GitHub Issues
Report a reproducible bug, a crash, or unexpected tool output — or request a feature. Public and tracked to resolution.
Discussions
Ask "how do I wire this into Claude / Cursor / my agent?" or compare approaches with the community and maintainers.
Email support
Private or account-specific help, billing, or anything you'd rather not post publicly.
Security
Report a vulnerability privately. Please don't open a public issue for anything exploitable — we prioritize these reports.
Specialized contacts
Route your message to the right team — each address is monitored.
-
partnerships@three.ws
AWS Marketplace, IBM, integrations & private offers -
privacy@three.ws
Data & privacy requests (GDPR / CCPA) -
legal@three.ws
Terms, EULA & legal notices -
dmca@three.ws
Copyright / DMCA takedown notices -
abuse@three.ws
Report abuse or platform misuse
What to expect
three.ws is an open-source project supported by its maintainers on a best-effort basis.
Before you open an issue
A few minutes here usually turns three round-trips into one.
Check your environment variables
Most "it won't start" reports are a missing required var — MCP_SVM_PAYMENT_ADDRESS, WATSONX_API_KEY, and WATSONX_PROJECT_ID (or WATSONX_SPACE_ID). See the README.
Reproduce with the MCP inspector
See the raw tool input/output: npx -y @modelcontextprotocol/inspector npx -y @three-ws/ibm-x402-mcp
Verify your IBM credentials independently
Create or check an API key at cloud.ibm.com/iam/apikeys, and confirm the project id under watsonx.ai project → Manage → General.
What to include in a bug report
The more of this you give us up front, the faster we can reproduce.
- The tool you called —
ibm_granite_chat,ibm_granite_code,ibm_granite_embed,ibm_granite_analyze, oribm_granite_forecast. - Your package version and Node version (
node -v— this server needs Node ≥ 20), plus your MCP client and OS. - The region you target via
WATSONX_URL(defaults tous-south) and the full error text. - Redact secrets. Never paste an API key, private key, or wallet seed. A truncated public Solana address is fine. For payment issues, the public transaction signature helps.
x402 MCP for IBM Granite
Pay-per-use IBM Granite — chat, code, embeddings, analysis, and time-series forecasting — settled in USDC on Solana. Listed on IBM Cloud Partner Center.
Dedicated docs & support for the MCP server
End users pay USDC on Solana per call — no IBM Cloud account required. Server operators supply IBM credentials and a receiving wallet. The full support guide covers payment vs. inference issues, scope, and how to tell a three.ws problem from an IBM platform problem.