Cline SingleOps MCP by usefulapi singleops_list_custom_inputs
How to: Cline SingleOps MCP by usefulapi singleops_list_custom_inputs
Add SingleOps MCP by usefulapi to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"singleops": {
"url": "https://singleops.usefulapi.io/mcp"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something singleops_list_custom_inputs does. Cline lists the server's tools on connect and calls singleops_list_custom_inputs itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that SingleOps MCP by usefulapi's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.