If your tool supports connecting to MCP servers, find the integration settings page to set up a new connection. Your tool might also call these “custom connectors”, “tools”, “integrations”, or “plugins”.

When you’re asked for the “MCP Server URL”, provide Delve’s MCP endpoint:

<https://mcp.delve.news/mcp>

If your tool asks for a “transport” or “protocol”, choose “HTTP” or “Streamable HTTP”. Tools that only support “HTTP+SSE” (which has been deprecated in the MCP spec) may not connect successfully, though you can try this as a fallback.

If your tool only supports “local” or “stdio” transports, you can use the mcp-remote package to connect to Delve, e.g.:

npx -y mcp-remote <https://mcp.delve.news/mcp>

If your tool asks about authentication, choose OAuth. You don’t need to provide a “Client ID” or “Client Secret”.