Contributing to Continue with Model Context Protocol (MCP)

What You'll Build

Master using the Continue Docs MCP to contribute documentation, create cookbooks, and maintain consistency across Continue’s docs - all through natural language prompts.

Prerequisites

Before starting, ensure you have:

Continue account with Hub access
Read: Contributing to Continue Documentation for setup instructions
Forked the continuedev/continue repository
Node.js 20+ and Continue CLI installed

This cookbook assumes you’ve read the setup in the CONTRIBUTING guide. If you haven’t, start there first.

Continue Docs MCP Setup

Fastest Path to Success

Use the pre-built Docs Assistant - Mintlify agent that includes the Continue Docs MCP and is ready to use immediately.

⚡ Quick Start (Recommended)
🛠️ Custom Agent

# From your Continue docs directory
cn --config continuedev/docs-mintlify

This agent includes:

Continue Docs MCP for searching Continue documentation
Mintlify formatting rules for proper component usage
Documentation-focused prompts for common tasks

What is the Continue Docs MCP?

Continue Docs MCP

A Model Context Protocol server built with Mintlify’s MCP generation that enables semantic search across Continue documentation. Learn more →

The MCP helps you:

Find examples from existing documentation
Maintain consistency with established patterns
Source accurate information about Continue features
Write better documentation faster

Documentation Workflows with Prompts

🆕 Creating a New Cookbook

Cookbooks show how to use Continue CLI with specific tools or services. Here’s how to create one using the Continue Docs MCP:

Research Existing Cookbooks

cn --config continuedev/docs-mintlify

Prompt:

"Show me the structure of existing MCP cookbooks in the Continue docs.
I want to create a cookbook for GitHub MCP."

The agent will find examples like the dlt, Snyk, and Sanity cookbooks.

Source Official Documentation

Prompt:

"Using the Continue Docs MCP, find information about how GitHub MCP works.
Then search the web for the official GitHub MCP documentation and combine
both sources to create a cookbook following the same structure as the
dlt cookbook."

The agent will:

Search Continue docs for MCP patterns
Fetch GitHub MCP official documentation
Combine both sources
Generate a cookbook with consistent formatting

Add to Navigation

Prompt:

"Add my new github-mcp-continue-cookbook.mdx to the docs.json navigation
under the Cookbooks section."

Preview and Iterate

npm run dev
# Visit http://localhost:3000

Refine with prompts:

"Add more examples to the troubleshooting section"
"Include a CI/CD workflow example using GitHub Actions"
"Add authentication setup using environment variables"

Pro Tip: The agent uses the Continue Docs MCP to maintain consistency with existing cookbooks automatically.

✏️ Updating Existing Documentation

Find the Documentation

Prompt:

"Where is the MCP tools documentation located? Show me the file path."

Make Targeted Updates

Prompt:

"Update the MCP tools documentation at docs/customization/mcp-tools.mdx
to include information about the new Slack MCP server. Use the Continue
Docs MCP to find examples of how other MCP servers are documented, then
add a similar section for Slack."

📝 Adding New Guides

Research Similar Content

Prompt:

"I want to create a guide for setting up Continue with Amazon Bedrock.
Search the Continue docs for similar model provider setup guides and
show me the common structure they follow."

Create the Guide

Prompt:

"Create a new guide at docs/guides/amazon-bedrock-setup.mdx following
the structure you found. Include:
- Prerequisites
- Step-by-step setup with code examples
- Configuration options
- Troubleshooting common issues

Use the Continue Docs MCP to find accurate information about Continue's
model provider configuration."

Add Navigation Entry

Prompt:

"Add this guide to docs.json under the Model Providers section"

Real-World Cookbook Examples

Example 1: PostgreSQL MCP Cookbook

Prompt:

"Create a cookbook for using Continue with PostgreSQL MCP. Follow the same
structure as the dlt cookbook, but customize it for database operations.

Include these sections:
1. Quick start with pre-built agent
2. Manual setup with MCP configuration
3. Common database tasks (schema exploration, query writing, migrations)
4. Troubleshooting database connection issues

Use the Continue Docs MCP to find MCP configuration patterns and search the
web for PostgreSQL MCP documentation."

Example 2: Sentry Error Tracking Cookbook

Prompt:

"Create a cookbook showing how to use Continue to analyze Sentry errors.

The cookbook should demonstrate:
1. Setting up Sentry MCP integration
2. Querying recent errors
3. Analyzing error patterns with AI
4. Generating fixes for common errors
5. CI/CD integration for automated error analysis

Research the Snyk cookbook structure since it's also about error detection,
and adapt it for Sentry."

Example 3: OpenAPI Documentation Cookbook

Prompt:

"I want to create a cookbook for using Continue to work with OpenAPI specs.

Show how to:
1. Load OpenAPI specs into Continue's context
2. Generate API client code from specs
3. Create tests based on API endpoints
4. Update documentation when APIs change

Use the Continue Docs MCP to find how context providers work, then combine
that with OpenAPI MCP information."

Advanced Prompt Patterns

Multi-Source Research

"Use the Continue Docs MCP to understand how agents
work in Continue, then search the web for Anthropic's
Computer Use MCP. Create a cookbook showing how to
combine Continue agents with Computer Use for
automated testing."

Cross-Reference Documentation

"Find all mentions of MCP servers across Continue
documentation. Then create a comprehensive reference
page that links to all MCP-related guides and
configurations."

Consistency Checking

"Review all cookbook files in docs/guides/ and check
if they follow the same structure. List any
inconsistencies and suggest updates to make them
uniform."

Example Extraction

"Extract all code examples showing MCP server
configuration from the Continue docs. Format them
as a single reference page with explanations for
each pattern."

Testing Your Documentation

Local Preview

cd docs
npm run dev
# Visit http://localhost:3000

Validation Prompts

# Check formatting
"Review this documentation for Mintlify formatting issues and fix any problems"

# Verify links
"Check all links in this file and ensure they point to existing documentation"

# Test code examples
"Verify that all code examples in this cookbook are syntactically correct"

Submitting Your Contribution

Prompt:

"Create a pull request with my documentation changes and use the repo's
PR template to write the description"

The agent will:

Create a feature branch
Stage and commit your changes
Push to your fork
Generate a PR description following the template
Open the PR for review

See the full Contributing Guide for manual PR submission details.

Automated Documentation Checks with GitHub Actions

Add automated documentation checks to your PR workflow using the Continue Docs MCP agent:

.github/workflows/docs-check.yml

name: Documentation Check

on:
  pull_request:
    types: [opened, synchronize]
    paths:
      - 'core/**'
      - 'extensions/**'
      - 'packages/**'
      - 'gui/**'

jobs:
  check-docs:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Install Continue CLI
        run: npm i -g @continuedev/cli

      - name: Analyze Changes for Documentation Needs
        id: analyze
        env:
          CONTINUE_API_KEY: ${{ secrets.CONTINUE_API_KEY }}
        run: |
          echo "🔍 Analyzing code changes for documentation needs..."

          # Get changed files
          git diff origin/${{ github.base_ref }}..HEAD --name-only > changed_files.txt

          # Create detailed diff
          git diff origin/${{ github.base_ref }}..HEAD > changes.diff

          # Use Continue agent to check if docs need updates
          PROMPT="Review these code changes and determine if documentation updates are needed.

          Changed files: $(cat changed_files.txt | tr '\n' ' ')

          Consider:
          - New features or APIs
          - Breaking changes
          - New configuration options
          - Modified CLI commands
          - New MCP integrations

          If docs updates are needed, specify which files in docs/ should be updated.
          If no updates needed, respond with 'NO_DOCS_NEEDED'.
          Be specific and concise."

          cn --config continuedev/docs-mintlify -p "$PROMPT" --auto > analysis.md || {
            echo "⚠️ Analysis failed"
            echo "needs_docs=false" >> $GITHUB_OUTPUT
            exit 0
          }

          if grep -q "NO_DOCS_NEEDED" analysis.md; then
            echo "needs_docs=false" >> $GITHUB_OUTPUT
          else
            echo "needs_docs=true" >> $GITHUB_OUTPUT
          fi

      - name: Post Documentation Recommendation
        if: steps.analyze.outputs.needs_docs == 'true'
        env:
          GH_TOKEN: ${{ github.token }}
        run: |
          echo "📝 Creating PR comment with documentation recommendations..."

          cat > pr-comment.md <<'EOF'
## 📚 Documentation Update Recommended

Based on the code changes in this PR, documentation updates may be needed:

EOF

          cat analysis.md >> pr-comment.md

          cat >> pr-comment.md <<'EOF'

---

### Next Steps

1. Review the suggested documentation areas above
2. Update relevant files in the `/docs` folder
3. Consider updating:
   - API references for interface changes
   - Guides for workflow changes
   - Configuration docs for new settings
   - MCP cookbooks for new integrations

### Resources
- [Contributing to Docs](/CONTRIBUTING)
- [Continue Docs MCP Cookbook](/guides/continue-docs-mcp-cookbook)

*This analysis was generated using the Continue Docs MCP agent.*
EOF

          gh pr comment ${{ github.event.pull_request.number }} --body-file pr-comment.md

      - name: Add Label
        if: steps.analyze.outputs.needs_docs == 'true'
        env:
          GH_TOKEN: ${{ github.token }}
        run: |
          gh pr edit ${{ github.event.pull_request.number }} --add-label "docs-needed"

This workflow uses the Continue Docs MCP agent to analyze code changes and automatically comment on PRs when documentation updates are recommended.

Documentation MCP for Other Projects

Want to create documentation MCPs for your own projects? Mintlify makes it easy:

Set Up Mintlify Docs

npm i -g mintlify
mintlify init

MCP Auto-Generated

Mintlify automatically generates an MCP server for your documentation, enabling semantic search.Learn more about Mintlify MCP generation →

Publish to Continue Hub

Share your docs MCP on Continue Hub so others can use it with Continue agents.

The Continue Docs MCP itself was built this way!

Key Prompts Cheat Sheet

Task	Prompt
Find structure	”Show me the structure of existing cookbooks in Continue docs”
Create cookbook	”Create a cookbook for [tool] MCP following the dlt cookbook structure”
Update docs	”Update [file] to include information about [feature], using Continue Docs MCP to find examples”
Add navigation	”Add [file] to docs.json under the [section] section”
Check consistency	”Review this file for consistency with other Continue documentation”
Fix formatting	”Review for Mintlify formatting issues and fix any problems”
Extract examples	”Find all examples of [topic] in Continue docs”
Research feature	”Use Continue Docs MCP to explain how [feature] works in Continue”

Resources

Continue Documentation

Contributing Guide - Setup and submission process
Continue Docs MCP Reference - MCP server details
- Understanding Configs - How configs work

Mintlify

Community

Continue Discord - #documentation channel
GitHub Discussions

Next Steps

Start Contributing

Set up your environment

Use Docs Agent

Install pre-built agent

Browse Cookbooks

See cookbook examples

Join Discord

Get help from community

Guides

Cookbooks

What You'll Build

​Prerequisites

​Continue Docs MCP Setup

Fastest Path to Success

​What is the Continue Docs MCP?

Continue Docs MCP

​Documentation Workflows with Prompts

​🆕 Creating a New Cookbook

​✏️ Updating Existing Documentation

​📝 Adding New Guides

​Real-World Cookbook Examples

​Example 1: PostgreSQL MCP Cookbook

​Example 2: Sentry Error Tracking Cookbook

​Example 3: OpenAPI Documentation Cookbook

​Advanced Prompt Patterns

Multi-Source Research

Cross-Reference Documentation

Consistency Checking

Example Extraction

​Testing Your Documentation

​Local Preview

​Validation Prompts

​Submitting Your Contribution

​Automated Documentation Checks with GitHub Actions

​Documentation MCP for Other Projects

​Key Prompts Cheat Sheet

​Resources

​Continue Documentation

​Mintlify

​Community

​Next Steps

Start Contributing

Use Docs Agent

Browse Cookbooks

Join Discord

Prerequisites

Continue Docs MCP Setup

What is the Continue Docs MCP?

Documentation Workflows with Prompts

🆕 Creating a New Cookbook

✏️ Updating Existing Documentation

📝 Adding New Guides

Real-World Cookbook Examples

Example 1: PostgreSQL MCP Cookbook

Example 2: Sentry Error Tracking Cookbook

Example 3: OpenAPI Documentation Cookbook

Advanced Prompt Patterns

Testing Your Documentation

Local Preview

Validation Prompts

Submitting Your Contribution

Automated Documentation Checks with GitHub Actions

Documentation MCP for Other Projects

Key Prompts Cheat Sheet

Resources

Continue Documentation

Mintlify

Community

Next Steps