---
schema_version: "1"
id: 4f8c35f010f3518f5711a74b5deb7a294a2220a90e9fba5e25dfb750142167e3
title: Untitled
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/einsteinfordevs/guides/files/devagent-mcpservers.md
canonical_url: https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/devagent-mcpservers.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b50214db041b9ace4eafcc469d54ccb9cf2c964da6ae1cf3c308e83ef0013b54
products:
  - Agentforce Vibes Developer Guide (Deprecated)
  - salesforcedx
---
## Connect to Remote MCP Servers

Remote MCP servers extend Agentforce's capabilities beyond built-in Salesforce tools by connecting to external services, APIs, and third-party platforms. This allows Agentforce to integrate with your entire development ecosystem.

### Understand Remote MCP Servers

Remote MCP servers are external services that expose tools and resources through the Model Context Protocol. Unlike built-in servers that run locally, remote servers:

- **Operate Over Networks**: Connect via HTTPS endpoints to cloud-hosted services.
- **Extend Capabilities**: Add functionality not available in built-in Salesforce servers.
- **Require Authentication**: Often need API keys or OAuth tokens for secure access.

**Unified Development Experience**
By connecting remote servers, you create a seamless workflow where Agentforce can:

- Access your entire development toolchain from one interface.
- Coordinate actions across multiple platforms.
- Maintain context across different services and tools.

### Access the MCP Servers Interface

To access the MCP Servers interface in Agentforce:

1. Click the Agentforce icon in the VS Code Activity Bar.
2. Click the icon (![server icon](https://developer.salesforce.com/media/einsteinfordevs/server.png)) in the top right corner of the Agentforce panel to open the MCP Servers interface.

The MCP Servers interface is divided into three main tabs:

- **Marketplace**: Discover and install pre-configured MCP servers (if enabled).
- **Remote Servers**: Connect to existing MCP servers via URL endpoints.
- **Installed**: Manage your connected MCP servers.

### Add Remote MCP Servers

1. Click the **Remote Servers** tab in the MCP interface.

2. Enter the following information:

   - **Server Name**: Choose a descriptive, unique name (e.g., "GitHub Integration", "Company Database").
   - **Server URL**: Enter the complete endpoint URL from the service provider.

3. Click **Add Server**.

Agentforce attempts to connect to the server and display the connection status. Verify the connection using the status indicators.

**note:** When connecting to a remote server, ensure you trust the source, as MCP servers can execute code in your environment. Always verify the server provider's credentials and security practices.

### Manage Connected Servers

Once added, your MCP servers appear in the "Installed" tab where you can monitor their status:

- 🟢 **Green Dot**: Connected and ready to use.
- 🟡 **Yellow Dot**: Connecting or experiencing warnings.
- 🔴 **Red Dot**: Disconnected or error state.

**Server Configuration Options**

Click on a server to expand its settings panel:

**Tools and Resources**

- View all available tools and resources from the server.
- Configure auto-approval settings for trusted tools.
- Review tool documentation and parameters.

**Request Timeout Settings**

- Set how long Agentforce should wait for server responses.
- Options range from 30 seconds to 1 hour.
- Adjust based on server performance and network conditions.

**Server Management Actions**

- **Retry Connection**: Reconnect if the server becomes unresponsive.
- **Delete Server**: Remove the server from your configuration.
- **Enable/Disable**: Toggle server availability without deleting.

### Troubleshoot Connection Issues

**Server Connection Failures**

1. Verify the server URL is correct and accessible.
2. Check that the server is running and accepting connections.
3. Confirm network connectivity and firewall settings.
4. Use the **Retry Connection** button to attempt reconnection.

**Authentication Problems**

1. Verify API keys or tokens are valid and not expired.
2. Check that authentication credentials have required permissions.
3. Review the authentication method matches server requirements.

### Test Remote Server Functionality

Try these prompts to verify your remote server setup:

1. **Test Server Connection**

   ```
   User: "List the tools available from my GitHub server".
   Expected: Display of available GitHub integration tools.
   ```

2. **Test Tool Execution**

   ```
   User: "Create a GitHub issue for the bug we just discussed".
   Expected: Agentforce uses the GitHub server to create an issue.
   ```