Test an MCP connection

Use the MCP quick start in Applications -> your application -> Credentials to test a new application API key. Copy its cURL command and run it in a terminal. It lists the tools available to that application; the URL shown there is separate from the Gateway API URL.

The command includes the key because Optiak shows its full value only once. Treat the copied command as a secret; do not share or commit it.

You can also run the check with values stored in environment variables:

curl "$OPTIAK_MCP_URL" \
  -H "Authorization: Bearer $OPTIAK_API_KEY" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Set OPTIAK_MCP_URL to the URL in the quick start. It ends in /mcp.

Read the result

• A successful response has a result.tools list. An empty list means the connection works but no tools are currently available to that application.
• If authentication fails, check that the key belongs to this application and has not expired or been revoked.
• If tools are missing, check that the setup is active, assigned to the application, enabled in Modules -> Tools, and that any external connection is ready. See Tools.

MCP clients use the same gateway URL and application key. The client must support Streamable HTTP and an Authorization: Bearer <application-api-key> header.