Koskamo

web2wave MCP

A Model Context Protocol server for the web2wave platform that enables AI clients like Claude Desktop, Cursor, and Codex CLI to interact with web2wave features. It handles OAuth discovery automatically and requires users to provide a project API key obtained from the web2wave cabinet settings.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

web2wave MCP logo, by web2waveCommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-07Published by web2wave
You need:Add this URL in your client's "Add MCP server" dialogGet the key in the web2wave cabinet → Project Settings → API
MCP endpoint (Streamable HTTP)
https://mcp.web2wave.com/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Integrate web2wave MCP into AI clients like Claude Desktop or Cursor
  • Manage web2wave quizzes and paywalls via AI agents
  • Run experiments and handle subscriptions through MCP
  • Authenticate using OAuth and project API keys

Source and maintenance

Community listingRegistry 1.0.0
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
151 ms
95th percentile latency
151 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 151 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http web2wave-mcp https://mcp.web2wave.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add web2wave-mcp --url https://mcp.web2wave.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable web2wave-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "web2wave-mcp": {
      "url": "https://mcp.web2wave.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "web2wave-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.web2wave.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start web2wave-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "web2wave-mcp": {
      "type": "http",
      "url": "https://mcp.web2wave.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http web2wave-mcp https://mcp.web2wave.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.web2wave.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "web2wave-mcp": {
      "serverUrl": "https://mcp.web2wave.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like web2wave MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.