Try these checks in order.
1. Confirm the server address
Use exactly:
https://mcp.solnk.com/mcp
Do not add /sse, /api, or another path.
2. Remove the old connection and add it again
MCP clients can cache an earlier authorization attempt. Remove Solnk from the client, restart the client, add the server again, and complete the browser authorization from the beginning.
3. Check the sign-in method
- OAuth: make sure the browser returns to the same client that started the connection.
- API key: create a current
sk_...key in Solnk and include it as a Bearer token. Replace revoked or expired keys. - ChatGPT web: confirm the Solnk plugin is available and allowed by the workspace administrator.
- Other clients: confirm the client supports remote Streamable HTTP MCP and follow its current authentication flow.
4. Test without publishing
Ask the client to list Solnk tools, then ask it to list your connected accounts. This separates a connection problem from a publishing or social-account problem.
What common errors mean
| Message | What to do |
|---|---|
401 Unauthorized | Finish OAuth again or replace the API key. |
Invalid or expired API key | Revoke the old key and create a new one. |
| No Solnk tools appear | Remove and re-add the MCP server, then restart the client. |
| Tools appear but no social accounts are returned | Open Solnk and connect or reconnect the social account. |
| Solnk is not listed in ChatGPT | The plugin is not available to that account or has been disabled by the workspace. |
If it still fails, email contact@solnk.com with the client name and version, the exact error message, and the step that failed. Do not include your API key or access token.