[Continue](https://www.continue.dev/) is an open-source AI code assistant for Visual Studio Code. Because it speaks the **Model Context Protocol (MCP)**, Continue can discover and call the tools you publish through **ContextForge** - no plug-in code required. !!! tip "Gateway URL" - Direct installs (`uvx`, pip, or `docker run`): `http://localhost:4444` - Docker Compose (nginx proxy): `http://localhost:8080` ---
9 stars
0 votes
0 copies
0 views
Added October 11, 2026
ai-agentspythonbashdockergit
Works with
cli
mcp
Security analysis
B88/100
criticalSends environment variables or credentials to an external URL
Installs into .claude/skills of the current project.
Are you the author of 1901 Continue 4f371801?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tools-only-1901-continue-4f371801)
# Continue (VS Code Extension)
[Continue](https://www.continue.dev/) is an open-source AI code assistant for Visual Studio
Code.
Because it speaks the **Model Context Protocol (MCP)**, Continue can discover and call the
tools you publish through **ContextForge** - no plug-in code required.
!!! tip "Gateway URL"
- Direct installs (`uvx`, pip, or `docker run`): `http://localhost:4444`
- Docker Compose (nginx proxy): `http://localhost:8080`
---
## π§° Key Features
* β¨ **AI-powered completions, edits & chat**
* π **MCP integration** - dynamic tool list pulled from your gateway
* π **Bring-your-own model** - local Ollama, OpenAI, Anthropic, etc.
* π§ **Context-aware** - reads your workspace to craft better replies
---
## π Installation
1. **Install "Continue"**: `Ctrl β§ X` β search *Continue* β **Install**
2. **Open config**: `Ctrl β§ P` β *"Continue: Open Config"*
β edits **`~/.continue/config.json`**
---
## π Connecting Continue to ContextForge
There are **two ways** to attach Continue to a gateway:
| Transport | When to use | Snippet |
|-----------|-------------|---------|
| **SSE (HTTP)** | Remote / SSL / no local process | `<-- see Option A>` |
| **Stdio wrapper** | Local dev, no SSE, or auth-header issues | `<-- see Option B>` |
> For both options you still need a **JWT** or Basic auth if the gateway is protected.
### Option A - Direct SSE
```jsonc
// ~/.continue/config.json
{
"experimental": {
"modelContextProtocolServer": {
"transport": {
"type": "sse",
"url": "http://localhost:4444/servers/UUID_OF_SERVER_1/sse",
"headers": {
"Authorization": "Bearer ${env:MCP_AUTH}"
}
}
}
}
}
```
*Generate a token*:
```bash
export MCP_AUTH=$(python3 -m mcpgateway.utils.create_jwt_token -u admin@example.com --secret my-test-key)
```
### Option B - Local stdio bridge (`mcpgateway.wrapper`)
1. **Install the wrapper** (pipx keeps it isolated):
```bash
pipx install --include-deps mcp-contextforge-gateway
```
2. **Config in Continue**:
```jsonc
{
"experimental": {
"modelContextProtocolServer": {
"transport": {
"type": "stdio",
"command": "python3",
"args": ["-m", "mcpgateway.wrapper"],
"env": {
"MCP_SERVER_URL": "http://localhost:4444/servers/UUID_OF_SERVER_1",
"MCP_AUTH": "Bearer ${env:MCP_AUTH}",
"MCP_TOOL_CALL_TIMEOUT": "120"
}
}
}
}
}
```
> If you prefer Docker:<br/>
> replace `"command": "python3"` with `"command": "docker"` and use the same container
> arguments shown in the Copilot docs.
---
## π§ͺ Using Gateway Tools
Once VS Code restarts:
1. Open **Continue Chat** (`β₯ C` on macOS / `Alt C` on Windows/Linux)
2. Click **Tools** - your gateway's tools should appear
3. Chat naturally:
```
Run hello_world with name = "Alice"
```
The wrapper/Gateway executes and streams the JSON result back to Continue.
---
## π Tips
* **SSE vs stdio** - SSE is simpler in prod, stdio is great for offline or
header-free environments.
* **Multiple servers** - add more blocks under `"servers"` if you run staging vs prod.
* **Custom instructions** - Continue's *Custom Instructions* pane lets you steer tool use.
---
## π Resources
* π [Continue docs](https://docs.continue.dev/)
* π [MCP Spec](https://modelcontextprotocol.io/)
* π [ContextForge GitHub](https://github.com/ibm/mcp-context-forge)