Hosted MCP · no local package
Copy a client config, check the connection, then run one tool. Same endpoint for every client.
https://utilito.dev/mcpClick a client to copy its install config and open the steps.
claude mcp add --transport http --scope user utilito https://utilito.dev/mcp{
"mcpServers": {
"utilito": {
"type": "http",
"url": "https://utilito.dev/mcp"
}
}
}If it fails: If the server is missing, repeat the CLI command at user scope and inspect `/mcp` before retrying.
https://utilito.dev/mcpIf it fails: If no tools appear, review the custom connector URL in Claude settings; do not use the local Desktop config file for this hosted endpoint.
{
"mcpServers": {
"utilito": {
"url": "https://utilito.dev/mcp"
}
}
}If it fails: If Utilito is unavailable, validate `.cursor/mcp.json`, confirm the exact URL, and reload the Cursor window once.
{
"servers": {
"utilito": {
"type": "http",
"url": "https://utilito.dev/mcp"
}
}
}If it fails: If validation fails, confirm the top-level key is `servers`, then restart the Utilito server from `MCP: List Servers`.
https://utilito.dev/mcpIf it fails: If the client requires a configuration wrapper, follow that client’s documentation; there is no universal remote MCP JSON wrapper.
Safe first connection
Preview five fixed, benign requests, then explicitly connect to this site's same-origin /mcp endpoint. The check cannot accept a custom endpoint, token, or payload.
POST /mcp{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-06-18",
"capabilities": {},
"clientInfo": {
"name": "utilito-connection-doctor",
"version": "1.0.0"
}
}
}POST /mcp{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list",
"params": {}
}POST /mcp{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "search_tools",
"arguments": {
"query": "json repair",
"limit": 5
}
}
}POST /mcp{
"jsonrpc": "2.0",
"id": 4,
"method": "tools/call",
"params": {
"name": "get_tool_schema",
"arguments": {
"tool_id": "json-repair"
}
}
}POST /mcp{
"jsonrpc": "2.0",
"id": 5,
"method": "tools/call",
"params": {
"name": "run_tool",
"arguments": {
"tool_id": "json-repair",
"input": {
"input": "{name:\"Ada\",items:[1,2,],}"
},
"options": {},
"response_mode": "compact"
}
}
}Not run. Review every request above, then choose Run connection check.
Receipt appears after an explicit run.Next action: Install a client profile above, then use this receipt to compare protocol behavior without copying response bodies or schemas.
Open Claude Code, run `/mcp`, and confirm Utilito exposes five tools.
Open official client docsEnable the connector in a conversation and confirm Utilito exposes five tools.
Open official client docsReload Cursor and confirm the Utilito server exposes five tools.
Open official client docsRun `MCP: List Servers`, select Utilito, and confirm five tools are listed.
Open official client docsList tools and confirm the five bounded router operations before sending input.
Open official client docsDiscover the JSON repair tool, inspect its schema, then run one bounded deterministic repair. Same sequence for every client. Or use the API playground.
{
"query": "repair malformed JSON",
"limit": 3
}{
"tool_id": "json-repair"
}{
"tool_id": "json-repair",
"input": {
"input": "{name:\"Ada\",items:[1,2,],}"
},
"response_mode": "compact"
}Browser multi-tool paths: product workflows.
search_tools, then one schema — not the full catalog.