Claude Desktop is Anthropic’s desktop application and supports local MCP servers as well as remote connectors. This guide configures a remote server and verifies access using a read tool call.
What Is Claude Desktop?#
Claude Desktop is Anthropic’s official desktop app. It is available for macOS and Windows, with Linux in beta. Remote MCP connectors also work in Claude on the web; Desktop additionally supports locally launched MCP servers and Desktop Extensions.
This means you can connect external tools directly into Claude, without workarounds. Claude can then not only generate text but actively interact with your business tools -- create contacts in your CRM, triage emails, analyze documents.
Prerequisites#
- Claude Desktop installed (free from anthropic.com)
- A StudioMeyer MCP product with the appropriate account and authorization (available in our tools overview)
- 5 minutes
Step 1: Install Claude Desktop#
If you haven't already, download Claude Desktop:
- macOS: Directly from anthropic.com or via Homebrew
- Windows: Installer from anthropic.com
After installation, sign in with your Claude account. Chat is available on Free too. Code and Cowork features and organization approvals depend on your plan and surface. Use the official download for your operating system.
Step 2: Distinguish Remote from Local#
The StudioMeyer addresses in this guide are remote MCP endpoints: the provider runs the server and Claude connects over HTTPS. Configure these in Settings → Connectors. They do not belong as url and headers entries in the local claude_desktop_config.json.
The local configuration file is for servers launched on your computer, for example through command and args. Claude Desktop also supports Desktop Extensions for local servers. A local server can access files on your machine; a remote connector does not gain that access merely by being connected. In either case, tool results can be sent to the cloud model.
Step 3: Add a Remote Connector#
- Open Settings → Connectors and the option to add a custom connector.
- Enter a clear name and the MCP URL confirmed by the provider. For StudioMeyer Memory, it is
https://memory.studiomeyer.io/mcp. - Save the connector and start the offered connection or sign-in flow.
- Sign in to the correct provider account and review the requested permissions. An OAuth server uses browser authorization. An API key is not a universal requirement for MCP products.
- Enable the tools you need in the chat. Start with a read operation.
Custom connectors are available on Free, Pro, Max, Team and Enterprise; Free supports one custom connector. Organization owners and administrators can control availability and approvals. If the option is missing, check your account, workspace and the current official instructions first.
Connect More Products#
Add each additional remote server separately under Connectors. Authentication and permissions can differ by product. The tools overview describes available products; use their current setup instructions rather than guessing endpoint URLs. Crew is a Labs application, not a generally available live connector in this guide.
Step 4: Check the Connection and Tools#
A remote connector does not require editing local JSON or fully restarting the app. Check its status in Connectors, then open a new chat and confirm it is enabled for that chat.
Local servers use a different workflow: follow that server’s installation, configuration and restart instructions. On macOS the file is ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it is %APPDATA%/Claude/claude_desktop_config.json. Never save credentials in a public repository.
Step 5: Test with a Read Operation#
For example, ask:
"Which tools from the connected Memory server are available in this chat? Find the last decision about the website redesign and identify the entry you found."
Check the visible tool call and result. Claude saying that it is connected is not itself a connection test. For a CRM, start by listing existing contacts or leads. Test creation, updates and deletion only with test data and explicit approval rules.
Troubleshooting#
No Tools Available#
Check that the correct connector is connected and enabled in the chat. Check workspace approvals and plan limits. For a local server, also check installation, launch command, JSON syntax and server logs.
Connection Failed#
Check the exact MCP URL, internet connection and reachability of that product’s server. HTTPS over port 443 must be allowed. Remote connectors are reached from Anthropic’s infrastructure; a service available only inside your local network needs a suitable connection.
Authentication Error#
Disconnect and reconnect the connector. Check the provider account, permissions and any required active license. Use the product’s actual authentication method; a made-up bearer key or wrong prefix does not fix an OAuth error.
Best Practices#
Connect one server at a time and begin with reading. Before write operations, review the data and functions authorized. An MCP connector provides access, but does not guarantee that every request will run correctly or without approval.
Keep the desktop app and servers updated. macOS and Windows can update through the app; Linux follows the installed package’s update process. Review newly available tools or permissions before using them.
What's Next?#
With Claude Desktop and a configured MCP server, you have a powerful setup. Claude can now not only answer questions but actively take action -- in your real business tools. To see where Claude Desktop sits next to Claude Code and the API, our Claude guide for 2026 lays out the whole ecosystem.
Discover all available MCP products in our tools overview and expand your setup with tools that fit your workflow.
Sources and product status#
Remote MCP in Claude connectors / Local MCP servers in Claude Desktop / Claude Desktop platforms and installation
