POST /mltk/mcp_connection

Description. Create a new MCP connection. The token is moved into Splunk passwords storage; the KV record only carries a reference.

Body (JSON) — SPLUNK type.

{
  "name":        "splunk_mcp",
  "type":        "SPLUNK",
  "description": "Internal Splunk MCP",
  "details": {
    "url":   "https://mcp.example.com/services/mcp",
    "token": "bearer-token-here"
  }
}

Body (JSON) — ATLASSIAN type.

{
  "name":        "atlassian_mcp",
  "type":        "ATLASSIAN",
  "description": "Jira / Confluence MCP",
  "details": {
    "url":                     "https://mcp.atlassian.com/v1/sse",
    "token":                   "oauth-token",
    "client_id":               "...",
    "client_secret":           "...",
    "refresh_token":           "...",
    "is_auto_refresh_enabled": true
  }
}

Errors. 400 (validation: empty name, invalid URL, unsupported type), 409 (duplicate name), 403 (capability/ACL).

Example.

curl -sk -u "$SPLUNK_USER:$SPLUNK_PASSWORD" -X POST 
  -H "Content-Type: application/json" 
  --data @- "$SPLUNK_HOST/servicesNS/nobody/Splunk_ML_Toolkit/mltk/mcp_connection?output_mode=json" <<'JSON'
{
  "name": "splunk_mcp",
  "type": "SPLUNK",
  "details": {
    "url":   "https://mcp.example.com/services/mcp",
    "token": "bearer-token-here"
  }
}
JSON