Claude Desktop discovers MCP servers through its connectors UI — there is no need to hand-edit a config file. Open Settings ⇒ Connectors ⇒ Add and paste your MCP server URL:
https://your-host/mcp
Leave any “bearer token” or “API key” field blank — OAuth is the default auth mode. Click Save / Connect.
Claude Desktop will:
https://your-host/oauth/authorize.
In that browser tab, enter your OWNSONA_LOGIN_USERNAME and
OWNSONA_LOGIN_PASSWORD from application.ini. Click
Allow on the consent screen. The browser hands the resulting
OAuth code back to Claude, which exchanges it for an access token +
refresh token and stores them locally. Subsequent calls use those
tokens automatically; you will not see the browser flow again until
the refresh token expires (30 days by default).
In any conversation, ask “what tools do you have?” You should see the nine OwnSona tools listed.
Some legacy versions of Claude Desktop read MCP servers from a JSON
config file rather than the connectors UI. If yours is one of them,
the config-file path is unchanged but the url field is the
only thing you need — no headers/bearer entry:
{
"mcpServers": {
"ownsona": {
"url": "https://your-host/mcp"
}
}
}
Config-file paths:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json (when supported)
Restart Claude Desktop after editing. The first request triggers the same browser-based OAuth login described above.
In a fresh conversation:
Please call the recall tool with the query "test".
Claude will invoke recall. Even on an empty store you’ll see
the tool call succeed with an empty matches array.