MCP Server Update: Introducing HTTP Streamable Protocol and Optional Headers

We are excited to announce a significant enhancement to our MCP (Model Context Protocol) Servers, introducing support for the new HTTP Streamable protocol and Optional Headers. This update is designed to empower our agents with the ability to integrate with an even wider variety of MCP servers, offering greater flexibility and robust connectivity. This article will explore the implications of these new features for you, our technically minded end-users.

Understanding the New HTTP Streamable Protocol

The new HTTP Streamable protocol is a crucial advancement for MCP Server connectivity. This new connection protocol for MCP is being introduced as a forward-looking replacement, particularly as older streaming mechanisms, such as Server-Sent Events (SSE), are being phased out or losing support on various platforms.

Leveraging Optional Headers for Enhanced Connectivity

The introduction of Optional Headers provides a vital layer of flexibility and security for your MCP Server connections.

Why Optional Headers?

Many MCP servers, especially those requiring secure access, demand specific authentication mechanisms. Optional Headers allow you to include necessary information, such as a Bearer Token, directly within your connection request.

Benefits of Using Optional Headers

• Authentication & Security: Securely connect to MCP servers that require authentication tokens (e.g., Bearer Tokens) for access.
• Increased Compatibility: Integrate with a broader range of third-party MCP servers that rely on custom headers for various purposes.
• Customization: Pass custom data for specific server configurations, routing, or content negotiation.

Impact and Integration Examples

The combined support for HTTP Streamable and Optional Headers significantly broadens the compatibility of our agents with diverse MCP server environments. This means more seamless integrations and fewer limitations when connecting to your preferred models and services.

Important Note for Zapier Users

For those utilizing Zapier for their automation workflows, please be aware: Zapier has begun to deprecate support for the SSE protocol. To ensure uninterrupted service and leverage the latest capabilities, you will need to:

1. Switch to the new HTTP Streamable protocol for your MCP Server connections.
2. Update the connection link for your MCP server within your Zapier configurations to reflect the new protocol.

We encourage you to make this transition promptly to avoid any service disruptions.

Integrating with n8n: A Practical Example

Here is a quick example of integrating TeamPal agent with n8n workflow using the new MCP server trigger mode:

1. Configure MCP Server Trigger Node: In n8n, ensure it's configured to use the new HTTP Streamable protocol. You could add a Bearer Token to better secure your Workflow. In this example, we use a simple MCP node with a Calculator tool

2. Adding Optional Headers: In the HTTP Request node's settings, locate the "Headers" section. Here, you can add key-value pairs. For instance, if your MCP server requires a Bearer Token, you would add a header like:

• Key: Authorization
• Value: Bearer YOUR_BEARER_TOKEN_HERE
• (Replace YOUR_BEARER_TOKEN_HERE with your actual token.)

3. Add n8n MCP server to your agent.

Conclusion & Next Steps

The addition of HTTP Streamable and Optional Headers marks a significant step forward in integrating with MCP Servers in the TeamPal system. We are committed to continuously enhancing our platform based on user needs and technological advancements.

We encourage all users to explore these new capabilities. Refer to our updated documentation for detailed setup instructions, or contact our support team if you have any questions.

Try It Now