Skip to content

Generic context names conflict with VS Code defaults: fetch and search #20

@IllyaMoskvin

Description

@IllyaMoskvin

I'm using the Atlassian MCP with VS Code via GitHub Copilot. First impressions are great.

However, after installing, I noticed that there's a new #fetch context, which is tied to the mcp_fetch tool. Copilot already has a built-in #fetch context. Now, I have to be mindful of which #fetch context I select!

Same thing for the mcp_search tool and the built-in #search context.

I think these context should be renamed/namespaced to something less generic, e.g. #atlassianFetch and #atlassianSearch.

mcp_atlassian-mcp_search - Search Jira and Confluence using Rovo Search (unified search)
mcp_atlassian-mcp_fetch - Get Jira issue or Confluence page by ARI (Atlassian Resource Identifier)
Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions