Docs
dev.continue/docs is an MCP server that surfaces docs.continue.dev reference content to your agent over streamable HTTP.
About
The Continue Docs MCP server exposes documentation from docs.continue.dev to AI clients through the Model Context Protocol. Developers adopting Continue for local or hybrid LLM coding assistance often waste time context-switching between the IDE, changelogs, and configuration guides when something fails or a new feature ships. Adding this remote server gives the agent a structured path to pull Continue-specific reference material while you tune models, rules, or MCP stacks in Cursor, Claude Code, or other compatible hosts. It is not a general web browser automation layer; it is a narrow doc surface for one product ecosystem. Use it when you are actively integrating Continue into your daily ship loop and want answers grounded in the vendor doc site rather than stale training data. Scope expectations accordingly: it helps with Continue configuration and usage questions, not arbitrary repository debugging unless your client combines it with other tools.
- Remote MCP endpoint at docs.continue.dev/mcp
- Streamable HTTP transport (server version 1.0.0)
- Purpose-built for Continue.dev documentation retrieval
- Lightweight alternative to manual doc tab switching during setup
- Fits MCP-enabled clients alongside Continue-oriented workflows
Docs by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http docs https://docs.continue.dev/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
What it does
Let your agent query official Continue.dev documentation through MCP while you configure Continue, models, and IDE workflows.
Who is it for?
Best when you're standardizing on Continue and want MCP-backed doc lookup during setup, upgrades, and troubleshooting.
Skip if: Skip if you're not using Continue, or anyone and needs live search across arbitrary repos instead of Continue’s doc site.
What you get
With the docs MCP remote registered, the agent can retrieve Continue.dev documentation in context while you finish IDE and agent configuration.
- In-editor access to Continue.dev documentation via MCP tools
- Faster Continue setup and upgrade without manual doc hunting
- Reduced hallucinated Continue configuration advice
By the numbers
- Remote URL https://docs.continue.dev/mcp
- Server version 1.0.0
- Streamable HTTP transport type
Recommended MCP Servers
0piFree, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.
100Hires AI ATS & Recruitment SoftwareOfficial 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.
123elec McpInterface MCP officielle du site marchand 123elec, catalogue, stock, panier, commandes.
1stayHotel booking MCP server.2
2D Assets MCPMCP server for generating advanced mock 2D PNG assets for game prototypes.43D MeshWeaverMesh spatial optimizer reducing geometric overhead in 3D assets.How it compares
Vendor documentation MCP, not a multi-app integration broker like Composio Rube.
FAQ
Who is dev.continue/docs for?
It is for developers and developers who use Continue and want their MCP-enabled agent to answer questions using the official docs.continue.dev corpus.
When should I use dev.continue/docs?
Use it while configuring Continue, wiring MCP servers, or debugging Continue-specific behavior during the Build phase of your agent toolchain.
How do I add dev.continue/docs to my agent?
Add the remote MCP server URL https://docs.continue.dev/mcp with streamable HTTP transport in your client’s MCP configuration, then invoke doc tools from a compatible agent session.