Understanding the Requirements

To connect Agentforce Vibes to a custom streamableHttp MCP with OAuth authentication, the MCP must meet certain requirements, including being added to the CORS in the authenticated Org.

Troubleshooting the Issue

When the “Allow” prompt fails to trigger a response, it is essential to check the Output Tab and Developer Tools for errors.

The Output Tab in the VS Code output console should be checked for handshake errors or protocol mismatches in the “Agentforce Vibes” and “Extension Host” channels.

The Developer Tools should be used to inspect the Console for URI redirection errors occurring when the browser attempts to pass the token back to VS Code.

Root Cause of the Issue

The root cause of the issue is likely due to the MCP not meeting the requirements to work with Vibes, or errors occurring during the authentication process.

Step-by-Step Solution

To resolve the issue, follow these steps:

example.js

// Ensure the MCP is added to the CORS in the authenticated Org
// Check the Output Tab and Developer Tools for errors
// Verify the MCP meets the requirements to work with Vibes

Checklist for Connecting Agentforce Vibes to a Custom MCP

Checklist

• Ensure the MCP is added to the CORS in the authenticated Org
• Check the Output Tab and Developer Tools for errors
• Verify the MCP meets the requirements to work with Vibes
• Use the Developer Tools to inspect the Console for URI redirection errors
• Check the “Agentforce Vibes” and “Extension Host” channels in the VS Code output console for handshake errors or protocol mismatches

Frequently Asked Questions

What is the purpose of adding the MCP to the CORS in the authenticated Org?

Adding the MCP to the CORS in the authenticated Org allows the MCP to be accessed by Agentforce Vibes.

How do I check the Output Tab and Developer Tools for errors?

The Output Tab and Developer Tools can be accessed in the VS Code output console and by using Help > Toggle Developer Tools, respectively.

What are the requirements for the MCP to work with Vibes?

The MCP must meet certain requirements, including being added to the CORS in the authenticated Org, and must not have any handshake errors or protocol mismatches.

How do I troubleshoot the issue when the “Allow” prompt fails to trigger a response?

Troubleshooting the issue involves checking the Output Tab and Developer Tools for errors, and ensuring the MCP meets the requirements to work with Vibes.