Connecting to Servers

Connecting to Servers

Once you've deployed an MCP server, you'll want to connect it to an LLM client like Claude. This guide covers everything you need to know about server URLs, connection methods, and troubleshooting.

Understanding MCP Server URLs

When you deploy a server on MCP.soy, it gets a unique URL that follows this pattern:

https://your-server-slug.mcp.soy

For example, if your server slug is weather-assistant, your server URL would be:

https://weather-assistant.mcp.soy

Connecting with Claude

Claude has built-in support for MCP servers. Here's how to connect your server:

Method 1: Claude Web Interface

1. Go to claude.ai/settings/connectors
2. Click "Add custom connector"
3. In the modal, enter:
   • Name: A friendly name for your server (e.g., "Weather Assistant")
   • Remote MCP server URL: Your server's URL from MCP.soy
4. Click "Add"

The server will now be available in all your Claude conversations!

Method 2: Claude Desktop App

If you're using the Claude desktop application:

1. Open Claude Desktop
2. Go to Settings → MCP Servers
3. Click "Add Server"
4. Enter your server details:
   • Name: Display name for your server
   • URL: Your MCP server URL
   • API Key: (Only if your server requires authentication)
5. Click "Save"

Authentication Methods

MCP.soy supports three authentication methods for your servers:

1. Open Access (No Authentication)

Best for:

• Testing and development
• Public tools with no sensitive data
• Demo servers

Connection: Just provide the server URL, no additional configuration needed.

2. API Key Authentication

Best for:

• Private servers
• Team-specific tools
• Production deployments

To connect with API key auth:

1. Get your API key from the server's settings page
2. When adding the server in Claude:
   • Provide the server URL
   • Enter the API key in the authentication field

3. OAuth Authentication

Best for:

• Enterprise integrations
• User-specific access
• Advanced permission models

OAuth servers will redirect you to authenticate when you first connect.

Testing Your Connection

After connecting a server, test it by:

1. Starting a new conversation in Claude
2. Asking Claude to list available tools:

   "What tools do you have available from my MCP servers?"

3. Claude should respond with a list including your server's tools
4. Try using a specific tool:

   "Can you use the [tool_name] tool to [perform action]?"

Connection Troubleshooting

If your server isn't working as expected, check these common issues:

Server Not Appearing in Claude

• Verify deployment: Ensure your server shows as "Deployed" in MCP.soy
• Check URL: Confirm you're using the correct server URL
• Refresh Claude: Try refreshing the page or restarting the app
• Clear cache: Sometimes clearing browser cache helps

Authentication Errors

• API Key issues:
  • Verify the key is copied correctly (no extra spaces)
  • Check if the key has expired
  • Ensure you're using the right key for the environment
• OAuth problems:
  • Check if your OAuth token has expired
  • Try re-authenticating
  • Verify OAuth provider settings

Tools Not Working

• Test in MCP.soy first: Use the built-in testing interface
• Check tool permissions: Some tools may require specific auth levels
• Verify input formats: Ensure Claude is sending correct parameters
• Review error messages: Claude will often show specific error details

Managing Multiple Servers

You can connect multiple MCP servers to Claude simultaneously:

• No conflicts: Each server's tools are namespaced
• Smart routing: Claude automatically uses the right server for each tool
• Organization: Use clear, descriptive names for easy identification

Disconnecting Servers

To remove a server connection:

In Claude Web:

1. Go to Settings → Connectors
2. Find your server in the list
3. Click the menu (⋮) and select "Remove"

In Claude Desktop:

1. Go to Settings → MCP Servers
2. Select the server
3. Click "Remove Server"

Advanced Connection Options

Environment-Specific URLs

You can maintain different versions for different environments:

• Development: https://your-server-latest.mcp.soy ($LATEST version)
• Staging: https://your-server-v0-9-0.mcp.soy (specific version)
• Production: https://your-server.mcp.soy (latest stable)

Note: Version numbers in subdomains use hyphens instead of dots (e.g., v1-0-0 for version 1.0.0).

Custom Headers

Some advanced configurations may require custom headers. These can be set in the desktop app's advanced settings.

Proxy Configuration

If you're behind a corporate proxy, Claude Desktop supports proxy settings in the advanced configuration.

Security Best Practices

When connecting to MCP servers:

• Use authentication: Always use API keys for production servers
• Rotate keys regularly: Change API keys periodically
• Limit permissions: Give servers only the access they need
• Monitor usage: Check your server logs for unusual activity
• Use HTTPS only: All MCP.soy servers use HTTPS by default

Integration with Other Clients

While this guide focuses on Claude, MCP is an open protocol. Other clients that support MCP include:

• MCP-compatible development tools
• Custom applications using the MCP SDK
• Other LLM platforms adopting MCP

The connection process is similar: provide the server URL and any required authentication.

Next Steps

Now that you're connected:

• Learn about authentication options for securing your servers
• Explore creating more tools for your server
• Check out example servers for inspiration
• Read about deployment best practices