Install one hosted MCP server, approve OAuth in your browser, and call convert_url on any public page to get clean Markdown back.
{
"name": "contextplusplus",
"type": "http",
"url": "https://mcp.contextplusplus.com/mcp"
}Installs the hosted Streamable HTTP server. VS Code discovers OAuth from the server and opens login when it connects.
/ setup in three steps
01
Pick your client or paste https://mcp.contextplusplus.com/mcp. The install config contains only the server URL — no tokens, secrets, or local npx process.
02
Your MCP client discovers the Supabase OAuth server, opens the context++ consent screen, and stores its own token after approval.
03
The server exposes one high-signal tool, convert_url, which returns the same LLM-ready Markdown the API and CLI surfaces use.
/ output proof
A single tool call returns structured Markdown, not raw HTML or noisy provider JSON. That keeps prompts deterministic and short.
This domain is for use in documentation examples without needing permission. Avoid use in operations.
illustrative shape — real output via convert_url / process
/ the catalog
live from GET /v1/services · v1.0.3
click any provider to preview context++ output
/ faq
No. The protocol endpoint stays at https://mcp.contextplusplus.com/mcp. This homepage only explains how to connect and use it.
No. This page is for the hosted MCP surface. Local development still exists, but most teams can just connect the hosted endpoint and authenticate.
No. Install links and snippets only configure the remote MCP URL. The client obtains and stores OAuth tokens after you approve the browser consent flow.
Yes, for manual configs. Use ctxpp as the local server name if your host lets you choose it. Plugin installs keep the canonical contextplusplus name so skills and tool references stay stable.
convert_url — one public URL in, clean Markdown out. The same backend quota and subscription model applies here as on the HTTP API.
/ pricing
CLI, MCP, and the HTTP API all sit on the same conversion engine and subscription model. Pick the surface that fits the workflow.
See pricing →For steady, predictable pipelines.
Higher limits for production load.
checkout via Stripe · POST /v1/billing/checkout · cancel anytime in the billing portal