Glossary · term181 of 202
STDIO transport
A way of connecting an MCP client and server over standard input and output streams rather than HTTP, where the spec requires clients to re-send subscriptions after a server crash.
also written as stdio
Related terms
resource subscriptionAn MCP feature where a client registers interest in specific resource URIs so it gets notified of changes. It was removed from the stateless spec because tracking subscribers required the server to remember state.view termsubscriptions/listenThe MCP request a client now sends listing every resource URI it wants updates on, replacing the server-side subscribe feature the spec removed.view term
At a glance
- cited by
- 3 posts
- categories
- 3
- first used
- apr 2026
Every Stateless MCP Server Rebuilds State SomewhereA stateless MCP server never deletes its state, it just relocates it. The measured wire cost, the three places it lands, and how to pick one of them on purpose.
7 Free Ways to Stop ChatGPT From Eating Your CPU, RAM, and DiskFix ChatGPT performance without spending a cent: diagnose high CPU, reduce RAM-heavy threads, stop disk churn, trim Git load, and disable unused MCP servers.
Building an MCP Server From Scratch (The Parts Nobody Explains)Build an MCP server in TypeScript from zero. Covers the handshake, Streamable HTTP transport, OAuth 2.1 auth, error codes the SDK swallows, and production deployment patterns.