Open
Description
Before submitting your bug report
- I believe this is a bug. I'll try to join the Continue Discord for questions
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: Windows
- Continue version: 1.0.8
- IDE version: 1.99.3 (user setup)
- Model: GPT-4o Mini
- config:
name: Local Assistant
version: 1.0.0
schema: v1
models:
- name: GPT-4o Mini
provider: openai
model: gpt-4o-mini
apiKey: sk-proj-****
chatOptions:
baseSystemMessage: >-
<important_rules>
Always include the language and file name in the info string when you write code blocks.
If you are editing "src/main.py" for example, your code block should start with ' src/main.py'
When addressing code modification requests, present a concise code snippet that
emphasizes only the necessary changes and uses abbreviated placeholders for
unmodified sections. For example:
/path/to/file
// ... rest of code here ...
{{ modified code here }}
// ... rest of code here ...
{{ another modification }}
// ... rest of code here ...
In existing files, you should always restate the function or class that the snippet belongs to:
/path/to/file
// ... rest of code here ...
function exampleFunction() {
// ... rest of code here ...
{{ modified code here }}
// ... rest of code here ...
}
// ... rest of code here ...
Since users have access to their complete file, they prefer reading only the
relevant modifications. It's perfectly acceptable to omit unmodified portions
at the beginning, middle, or end of files using these "lazy" comments. Only
provide the complete file when explicitly requested. Include a concise explanation
of changes unless the user specifically asks for code only.
</important_rules>
You are an expert software developer. You give helpful and concise
responses.
context:
- provider: code
- provider: docs
- provider: diff
- provider: terminal
- provider: problems
- provider: folder
- provider: codebase
mcpServers:
- name: sqlite-test-service
command: uvx
args:
- --from
- mcp-alchemy==2025.5.2.210242
- --refresh-package
- mcp-alchemy
- mcp-alchemy
env:
DB_URL: sqlite:///C:/Repos/mcp-alchemy/tests/Chinook_Sqlite.sqlite
connectionTimeout: 60000
Description
I'm following the steps outlined in the mcp-alchemy repository to integrate the MCP server with Continue, but I am encountering an issue when trying to connect to the database. I am able to successfully call the tool from a test code, but when I attempt to connect to the server using Continue client, I get the error message: "Error loading resources for MCP Server sqlite-test-service: Not connected". I see green dot as in the image.
To reproduce
- Follow the steps in https://github.com/runekaagaard/mcp-alchemy repository.
- Add the server in config.yaml
Log output
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Todo