AI client can't reach the MCP server
Symptom
Your AI client fails to connect to prompt2love with a network, timeout, or "server unreachable" error — before any login or tool call succeeds.
Cause
- The connector URL is wrong. prompt2love supports only a remote HTTPS MCP endpoint — not a local (
localhost) or non-HTTPS server. - A network issue is blocking the request: a firewall, VPN, corporate proxy, or temporary outage.
Fix
- Verify the URL is exactly https://prompt2love.com/api/mcp — HTTPS, no typos, no trailing path or port.
- Check connectivity: open https://prompt2love.com in a browser on the same machine. If it doesn't load, the problem is your network, not the connector.
- Disable a blocking VPN or proxy temporarily, or ask IT to allow prompt2love.com over HTTPS (port 443).
- Retry in your AI client. Many clients only re-check the server when you re-add or re-authorize the connector.
- Confirm your client supports remote HTTPS MCP connectors — local-only stdio servers won't work here.
prompt2love is a hosted, OAuth-protected remote MCP server. There is nothing to run locally; you only point your client at the HTTPS URL above.
Still stuck?
If the site loads but the client still can't connect, see OAuth connection issues for authorization issues or connect via ChatGPT, or ask in the community.