streamable-http-mcp-server

Create and configure Streamable HTTP MCP server connections for OpenAI Agents SDK.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/SalmanO7/Todo_Full-Stack --skill streamable-http-mcp-server-salmano7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: streamable-http-mcp-server
Source: https://github.com/SalmanO7/Todo_Full-Stack/tree/main/.claude/skills/streamable-http-mcp-server
Command: npx skills add https://github.com/SalmanO7/Todo_Full-Stack --skill streamable-http-mcp-server-salmano7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and configuration of Streamable HTTP MCP server connections for OpenAI Agents SDK.

Core Features & Use Cases

  • Create MCPServerStreamableHttp configurations
  • Configure HTTP connection parameters and authentication
  • Set up caching and retry mechanisms
  • Connect to HTTP-based MCP servers with direct connection management

Quick Start

Instantiate MCPServerStreamableHttp with your server URL and optional headers, then create an Agent that uses that MCP server for tool calls.

Frequently Asked Questions about streamable-http-mcp-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure an HTTP MCP server connection for OpenAI Agents SDK?

To configure an HTTP MCP server connection for OpenAI Agents SDK, you instantiate MCPServerStreamableHttp with your server URL and optional headers, then assign that MCP server to your Agent for tool calls.

What parameters are available for streamable HTTP MCP server management?

Streamable HTTP MCP server management supports constructor parameters including url, headers, timeout, sse_read_timeout, terminate_on_close, and httpx_client_factory, alongside caching options, tool filtering, and retry control policies.

Can I set up authentication and retry policies for MCP server connections?

Yes, you can set up authentication and retry policies for MCP server connections by configuring HTTP headers for authentication and defining retry control mechanisms during server instantiation.

Does this approach support direct HTTP MCP server management for production workflows?

Yes, this approach supports direct HTTP MCP server management for production workflows by applying parameterization, authentication, caching, and structured content usage to maintain stable server connections.

What is the best way to manage tool filtering and structured content in an MCP server?

The best way to manage tool filtering and structured content in an MCP server is to apply the built-in caching options and structured content usage parameters provided during the streamable HTTP connection setup.

When should I use terminate_on_close and sse_read_timeout in MCP server configuration?

Use terminate_on_close and sse_read_timeout in MCP server configuration when you need to manage connection lifecycle behavior and Server-Sent Events read timeouts for direct HTTP server workflows.