Choose CLI for terminals, scripts, CI, headless systems, or agents that can execute shell commands. Use the hosted backend and print clean Markdown to stdout.
/ choose your integration
CLI
Choose CLI for headless systems, automation, or agents that can reliably run shell commands. It prints clean Markdown to stdout.
Install the CLI →MCP
Choose MCP when a coding agent, desktop client, or chat app supports MCP tools. The wizard writes a private Bearer/Connect-URL configuration; no OAuth.
Install MCP →Advanced: install both with --all or --mcp --cli. Coding agents can use either path—prefer MCP when the host supports it well, otherwise use CLI.
npx -y contextplusplus@1.7.3 install --mode cli
node "<absolute url-to-markdown-cli skill>/scripts/contextplusplus.mjs" process https://example.com --format markdownConfigures the selected agent, one CLI-first skill, private authentication, and managed guidance. No global package or shell-profile edit is required.
/ setup in three steps
01
The installer configures the selected agent, authentication, one CLI-first skill, and managed guidance. Runtime calls execute the version-pinned MJS inside that installed skill, with no npm resolution, global binary, or shell-profile edit.
02
The interactive installer asks only for email device registration/sign-in and stores the scoped credential in the private user store. Unattended runs accept stdin or a protected credential file.
03
Run process against any supported public URL and feed stdout directly into agents, scripts, or local files.
/ output proof
The CLI returns the same cleaned Markdown the API and MCP surfaces produce, so your shell scripts and your agents stay in sync.
This domain is for use in documentation examples without needing permission. Avoid use in operations.
illustrative shape — real output via scrape / process
/ the catalog
live from GET /v1/services · v1.0.3
click any provider to preview context++ output
/ faq
No. The hosted backend is the default path. Local mode exists for development, but the published CLI is designed to work against the branded production API.
Yes. Feed the credential to install with --api-key-stdin or --api-key-file, then run the bundled MJS at the selected agent's stable skill path. The runtime reads the private credential store.
No. npx is only the setup, login, and repair control plane. Normal processing and research calls run the dependency-free MJS shipped inside the installed skill.
It is the same engine and quota model behind a terminal-first interface. Pick the surface that fits the workflow without changing the output shape.
/ 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