Skip to content

MCP tools are showing but are not called #5771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
maximelebastard opened this issue May 21, 2025 · 5 comments
Open
3 tasks done

MCP tools are showing but are not called #5771

maximelebastard opened this issue May 21, 2025 · 5 comments
Assignees
Labels
area:mcp Relates to Model Context Protocol (MCP) kind:bug Indicates an unexpected problem or unintended behavior os:mac Happening specifically on Mac

Comments

@maximelebastard
Copy link

Before submitting your bug report

Relevant environment info

- OS: macOS
- Continue version: 1.1.32
- IDE version: 1.100.2
- Model: any
- config: 
  
%YAML 1.1
---
version: 1.0.16
schema: v1

bedrock: &bedrock
  provider: bedrock
  env:
    region: eu-central-1
    profile: bedrock

models:
  - name: (aws) Anthropic Claude 3.5 Sonnet
    <<: *bedrock
    model: anthropic.claude-3-5-sonnet-20240620-v1:0
    roles:
      - chat
      - edit
      - apply
  - name: (aws) Anthropic Claude 3.7 Sonnet
    <<: *bedrock
    model: eu.anthropic.claude-3-7-sonnet-20250219-v1:0
    roles:
      - chat
      - edit
  - name: (aws) Anthropic Claude 3 Haiku
    <<: *bedrock
    model: anthropic.claude-3-haiku-20240307-v1:0
    roles:
      - chat
      - autocomplete

  - name: (aws) Cohere Rerank
    <<: *bedrock
    model: cohere.rerank-v3-5:0
    roles:
      - rerank

  - name: (aws) Cohere Embed Multilingual
    <<: *bedrock
    model: cohere.embed-multilingual-v3
    roles:
      - embed
      
  - name: (local) Qwen 2.5 autocomplete
    provider: ollama
    model: qwen2.5-coder:3b
    roles:
      - chat

context:
  - provider: file
  - provider: code
  - provider: open
  - provider: folder
  - provider: clipboard
  - provider: diff
  - provider: terminal
  - provider: docs
  - provider: web
    params:
      n: 5
  - provider: codebase
  - provider: tree
  - provider: url

prompts:
  - name: commit
    description: Create a commit message from staged files
    prompt: "{{input}}"

docs:
  - name: Symfony
    startUrl: https://symfony.com/doc/6.4/index.html

defaultCompletionOptions:
  maxTokens: 4096


mcp servers config: 
name: Weather MCP server
version: 0.0.1
schema: v1
mcpServers:
  - name: Weather
    command: npx
    args:
      - -y
      - "@h1deya/mcp-server-weather"
    env: {}

Description

When providing MCP server (here a basic weather example) and asking pretty directly the chat to use the MCP tools, tools are not called at all.

To reproduce

  1. Apply the provided MCP server configuration and make sure to use AWS Bedrock as a chat model, with an Anthropic tool-use compatible model like Sonnet 3.5
  2. Make sure the MCP tools are appearing in the extension in the MCP servers tab and in the tools tab. In my case, you should have getAlert and getWeather tools
  3. Start a new chat, in chat mode, and ask Tomorrow's weather in Palo Alto? (as suggested by the MCP server author)
  4. The chat does not use or asks to use the weather tool
  5. The LLM answers it doesn't know

Also, I don't know if it's normal, but tools do not appear as context providers when typing @ into the chat.

Log output

@dosubot dosubot bot added area:mcp Relates to Model Context Protocol (MCP) kind:bug Indicates an unexpected problem or unintended behavior os:mac Happening specifically on Mac labels May 21, 2025
@maximelebastard
Copy link
Author

Maybe related to #5762 but looks a bit different

@Patrick-Erichsen
Copy link
Collaborator

@maximelebastard are you in Chat mode rather than Agent by any chance? We're updating the UI to make this more clear soon, but let me know if that's the case.

@bojandjukic1
Copy link

Seeing the same thing with the following model set up

name: Local Assistant
version: 1.0.0
schema: v1
models:
- name: Llama 3.1 8B
  provider: ollama
  model: llama3.1:8b
  roles:
  - chat
  - edit
  - apply
- name: Qwen2.5-Coder 1.5B
  provider: ollama
  model: qwen2.5-coder:1.5b-base
  roles:
  - autocomplete
- name: Nomic Embed
  provider: ollama
  model: nomic-embed-text:latest
  roles:
  - embed
- name: Autodetect
  provider: ollama
  model: AUTODETECT
context:
- provider: code
- provider: docs
- provider: diff
- provider: terminal
- provider: problems
- provider: folder
- provider: codebase

mcpServers:
  - name: My MCP Server
    command: docker
    args:
        - run
        - -i
        - --rm
        - --mount
        - "type=bind,src=C:/tmp/scoped-folder,dst=/projects"        
        - mcp/filesystem
        -  /projects

The docs indicate that MCP servers should show up in the @ context menu but they do not, even though the servers list as healthy and running (green icon) and the tool use is populated to reflect the MCP server capabilities.

Any guidance of whether this is simple a model limitation of the model I'm using would be appreciated.

@bojandjukic1
Copy link

By the way when I add

...
context:
- provider: mcp
...

The context menu now shows up

Image

However it picks up no servers..

Image

@maximelebastard
Copy link
Author

@maximelebastard are you in Chat mode rather than Agent by any chance? We're updating the UI to make this more clear soon, but let me know if that's the case.

I'm indeed in chat mode
So MCP servers are only compatible with Agent Mode ? Is it a permanent limitation ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:mcp Relates to Model Context Protocol (MCP) kind:bug Indicates an unexpected problem or unintended behavior os:mac Happening specifically on Mac
Projects
Status: Todo
Development

No branches or pull requests

3 participants