Choose MCP when your coding agent, desktop client, or chat app supports native MCP tools. The smart installer writes private Bearer/Connect-URL configuration; no OAuth.
/ 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 installRecommended chooser. Pick MCP for hosts with MCP support or CLI for terminal/script workflows. Use --mcp to force this mode; advanced users can add both with --all.
/ setup in three steps
01
The wizard recommends MCP when it detects a supported non-headless host. Choose CLI instead for terminals, CI, or agents that run shell commands; use --all only when you need both.
02
npx -y contextplusplus@1.7.3 install signs you in, installs the workflow skill, and writes a separate private Connect URL for each selected target. Static plugins remain credential-free and do not create a second MCP connection.
03
Use get-research-consultancy for the evidence plan, web-search for ranked leads, and scrape-link for source-grounded extraction. consult, search, scrape, and convert_url remain compatibility aliases.
/ output proof
Tool calls return structured Markdown, not raw HTML or noisy provider JSON. scrape-link can also run source-grounded extraction when LLM config is enabled.
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 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. Public snippets, plugins, project files, and deep links contain no credential. The smart installer writes target-specific Connect URLs only into private user config. GUI users deliberately copy one target URL from the authenticated dashboard.
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.
get-research-consultancy, web-search, scrape-link, plus the consult, search, scrape, and convert_url compatibility aliases. Quota errors include a safe usage link and explicit retry guidance.
/ 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