Doc: Fixes #16186: missing word added

[taw00]

This is a trivial fix. There's a missing 'to' in a sentence. :)

Note.
I have read the CLA Document and I hereby sign the CLA

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[coderabbitai]

.

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -eu

file=$(git ls-files | awk '$0 == "readme/apps/ai_mcp.md" {print; found=1} END {if (!found) exit 1}')
printf '%s\n' "== target context =="
sed -n '1,80p' "$file"

printf '%s\n' "== related MCP and Claude references =="
rg -n -i -C 3 'claude|mcp-remote|http|claude_desktop_config' "$file" readme 2>/dev/null | head -240

printf '%s\n' "== repository status =="
git status --short

Repository: laurent22/joplin

Length of output: 37644

---

🌐 Web query:

Anthropic Claude Desktop custom connectors remote MCP local claude_desktop_config HTTP MCP server mcp-remote documentation

💡 Result:

To connect remote MCP servers to Claude Desktop, you must use one of two distinct methods depending on your requirements and the server's authentication mechanism. Note that Claude Desktop's claude_desktop_config.json file natively supports only local stdio-based MCP servers; it will not correctly parse a raw url field for remote HTTP servers and may remove such entries from your configuration [1][2][3]. 1. Using the Custom Connectors UI (Recommended for OAuth) This is the official method for connecting to publicly accessible remote MCP servers [4][5]. - Open Claude Desktop and go to Settings > Connectors. - Click "Add custom connector." - Enter your remote MCP server URL. - If required, provide an OAuth Client ID and Secret in the "Advanced settings." - Once added, Claude Desktop will manage the connection via Anthropic's cloud infrastructure [4][6]. This method is preferred as it is integrated, supports OAuth flows, and works consistently across other Claude clients [4][1]. 2. Using the mcp-remote Bridge (For Local/Development or Non-OAuth) If you need to test a remote server or require specific configuration (such as custom headers) that the UI does not support, you must use the mcp-remote proxy as a stdio-to-HTTP bridge within your claude_desktop_config.json [1][3][7]. - This approach tells Claude Desktop to launch a local process (mcp-remote) that communicates with the remote server via HTTP while presenting as a standard local stdio server to Claude [1][3]. - Edit your claude_desktop_config.json file (accessible via Settings > Developer > Edit Config) and add your server as follows: { "mcpServers": { "your-server-name": { "command": "npx", "args": ["-y", "mcp-remote", "https://your-remote-server-url/mcp"] } } } Important Considerations: - Remote vs. Local Connectivity: When using the Custom Connectors UI, connections originate from Anthropic's cloud infrastructure, meaning your server must be reachable over the public internet [4][6]. Conversely, when using the mcp-remote bridge, the connection originates from your local machine, allowing you to bridge local network services that are not publicly exposed [4][1][3]. - Configuration Stability: Do not attempt to add a url field directly into claude_desktop_config.json as the configuration schema will likely reject or delete the entry [2][3]. Always use the command and args format with mcp-remote when manual JSON configuration is required [1][7].

Citations:

• 1: https://designrevision.com/blog/claude-desktop-mcp-config
• 2: [BUG] Claude Desktop silently destroys claude_desktop_config.json when MCP server uses url field anthropics/claude-code#37286
• 3: https://startdebugging.net/2026/05/fix-http-mcp-server-url-wont-connect-in-claude-desktop/
• 4: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
• 5: https://dev.to/dennis-ddev/how-to-set-up-claude-desktop-with-mcp-servers-2026-guide-2fc7
• 6: https://www.getdrio.com/blog/mcp-setup-claude-desktop
• 7: https://developers.cloudflare.com/agents/guides/test-remote-mcp-server/index.md

---

Scope the HTTP limitation to local configuration.

When using claude_desktop_config.json, Claude Desktop does not connect directly to a local HTTP MCP server. Remote MCP servers can be connected through custom connectors.

Proposed wording

-Claude Desktop doesn't speak to HTTP MCP servers directly; it needs a small bridge called [`mcp-remote`](https://www.npmjs.com/package/mcp-remote).
+When using `claude_desktop_config.json`, Claude Desktop does not connect directly to a local HTTP MCP server; it needs a small bridge called [`mcp-remote`](https://www.npmjs.com/package/mcp-remote).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Claude Desktop doesn't speak to HTTP MCP servers directly; it needs a small bridge called [`mcp-remote`](https://www.npmjs.com/package/mcp-remote). You don't need to install it — it'll be downloaded automatically the first time.
	When using `claude_desktop_config.json`, Claude Desktop does not connect directly to a local HTTP MCP server; it needs a small bridge called [`mcp-remote`](https://www.npmjs.com/package/mcp-remote). You don't need to install it — it'll be downloaded automatically the first time.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@readme/apps/ai_mcp.md` at line 36, Update the Claude Desktop guidance to
scope the HTTP limitation specifically to local configuration via
claude_desktop_config.json: state that local HTTP MCP servers require the
mcp-remote bridge, while noting that remote MCP servers can be connected through
custom connectors.

[taw00]

I have read the CLA Document and I hereby sign the CLA