Continue.dev Integration
Continue.dev is an open-source AI code assistant for VS Code and JetBrains IDEs. This guide shows how to connect Snipara to Continue for documentation-aware coding assistance using Server-Sent Events (SSE) transport.
What You Get
MCP Tools in Chat
Access Snipara tools directly from Continue's chat interface using @snipara.
Open Source
Continue is fully open source. Use with any LLM provider (OpenAI, Anthropic, local models).
SSE Streaming
Real-time streaming responses via Server-Sent Events for fast, interactive conversations.
Prerequisites
- Continue.dev extension installed in VS Code or JetBrains IDE
- A Snipara project with at least one document indexed
- An API key from your Snipara dashboard
Setup
Step 1: Open Continue Configuration
In VS Code, open the Command Palette (Cmd/Ctrl + Shift + P) and search for "Continue: Open Config". This will open your ~/.continue/config.json file.
Step 2: Add MCP Server Configuration
Add the Snipara MCP server to your configuration using SSE transport:
{ "models": [...], "mcpServers": [ { "name": "snipara", "transport": { "type": "sse", "url": "https://api.snipara.com/mcp/PROJECT_ID/sse", "headers": { "X-API-Key": "YOUR_API_KEY" } } } ]}SSE Transport
Continue.dev uses Server-Sent Events (SSE) for streaming responses from MCP servers. The SSE endpoint is /mcp/PROJECT_ID/sse (note the /sse suffix).
Step 3: Replace Placeholders
Replace the following values:
PROJECT_ID- Your Snipara project ID (found in the project dashboard)YOUR_API_KEY- Your API key (starts withrlm_)
Step 4: Reload Continue
After saving the configuration, reload Continue by running "Continue: Reload Configuration" from the Command Palette.
Using Snipara in Continue
Once connected, you can use Snipara tools in Continue's chat interface:
@snipara How does the authentication system work?[Using rlm_context_query with max_tokens=4000]Based on your documentation, the auth system uses...Available Tools
The following Snipara tools are available through Continue:
rlm_context_queryQuery documentation with token optimization
rlm_askSimple question-answer queries
rlm_searchSearch for patterns (regex supported)
rlm_rememberStore facts, decisions, learnings
rlm_recallSemantically recall stored memories
rlm_decomposeBreak complex questions into sub-queries
rlm_multi_queryExecute multiple queries in one call
See the MCP Tools Reference for complete documentation of all 43 tools.
Workflow Examples
Query Documentation
@snipara How does the rate limiting work?[Using rlm_context_query with max_tokens=4000]Based on your documentation, rate limiting is implemented...Search for Code Patterns
@snipara Search for usages of useAuth hook[Using rlm_search with pattern="useAuth"]Found 12 matches in 5 files...Memory-Driven Development
Save a decision for later@snipara Remember: Using JWT for auth tokens because...Memory saved with type=decisionRecall later in a new session@snipara What did we decide about authentication?[Using rlm_recall with query="authentication"]Found decision: Using JWT for auth tokens because...Alternative: HTTP Transport
If your version of Continue doesn't support SSE, you can use the standard HTTP transport:
{ "mcpServers": [ { "name": "snipara", "transport": { "type": "http", "url": "https://api.snipara.com/mcp/PROJECT_ID", "headers": { "X-API-Key": "YOUR_API_KEY" } } } ]}Troubleshooting
- Verify your API key is correct and not expired
- Check that the project ID in the URL is correct
- Ensure you're using the SSE endpoint (
/mcp/sse) not the standard endpoint - Try the HTTP transport as an alternative
- Reload Continue configuration after saving changes
- Check the Continue output panel for error messages
- Ensure the mcpServers array is properly formatted JSON
- Try restarting VS Code/JetBrains
- Check your usage in the Snipara dashboard
- Upgrade your plan for higher limits
- Wait a minute for the rate limit to reset
- Check your network connection stability
- If using a VPN or proxy, try without it
- Consider using HTTP transport instead for more stable connections