MCP Server for continue.dev
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchC | Search the web for information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| echo |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| test/resource | Test project resource |
| documentation://test/docs |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'web_search' has a clear and distinct purpose that cannot be confused with any other tool in this set.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare against. The tool name 'web_search' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A server with only one tool feels thin and under-scoped for a general-purpose domain like 'continue.dev', which might imply broader functionality. While a single tool can be appropriate for highly specialized servers, this seems too minimal for the apparent scope.
The tool surface is severely incomplete for a server named for 'continue.dev', which likely involves development or coding assistance. A single web search tool leaves significant gaps, such as code analysis, file operations, or other development-related tasks, causing potential agent failures.