Superhuman Mail runs a remote MCP server at https://mcp.mail.superhuman.com/mcp. This guide covers what that server requires, why DSH cannot complete its interactive sign-in on its own, the stdio bridge Superhuman documents for desktop clients, and how to check the connection without letting an agent touch your inbox.
DSH MCP Integration Guides
DeepSeek Harness speaks the Model Context Protocol through the @deepseek-ai/dsh-mcp-client plugin. These four guides cover the servers people ask about most, including the part their own docs leave out for a harness: which transport DSH can drive, which server needs a local bridge, and what a first verification call costs.
Scope: DSH configuration only. Each guide names the operator of the server, links the source it was checked against, and states what was not verified by running it.
Google Stitch exposes an MCP server at https://stitch.googleapis.com/mcp. It is remote and header-authenticated, which makes it one of the simpler servers for DSH to call directly. This guide covers the API-key path, the Cordis row, the timeout that decides whether a slow generation looks like a broken connection, and the npm package you do not need.
Krea hosts an MCP server at https://api.krea.ai/mcp for image and video generation. DSH cannot run Krea's interactive consent screen, so the practical path is the API-token header — and that choice also decides which balance pays for the work.
Alpha Vantage maps its market-data endpoints onto MCP tools and publishes both a hosted endpoint and a local server. For DSH the local server is the documented route, because the hosted endpoint authenticates through a sign-in page — and the data tier, not the connection, is what limits you.
DSH loads MCP servers through the @deepseek-ai/dsh-mcp-client plugin. If you are new to it, start with the DSH MCP setup walkthrough, then come back for the server you actually want.