@chenpu17/web-bridge-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using DuckDuckGo - performs real-time web searches
Usage notes:
|
| web_fetchA | Fetches content from a specified URL and converts it to readable format
Usage notes:
|
| resolve-library-idA | Official Context7 library resolver. Use this first when the user asks about a library, framework, SDK, package, API usage, installation, configuration, migration, or code examples. Prefer this over web_search for software documentation tasks. Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Each result includes:
For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case. Selection Process:
Response Format:
For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have. |
| query-docsA | Official Context7 documentation query tool. Use this to retrieve authoritative docs and examples after you know the library ID. Prefer this over web_search/web_fetch for library and framework documentation. Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Do not call this tool more than 3 times per question. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools are clearly separated by purpose: web_search vs web_fetch are distinct (search vs retrieve URL), and resolve-library-id vs query-docs are distinct (resolve ID vs query docs). There is slight overlap between web_search and resolve-library-id for library queries, but explicit guidance to prefer Context7 tools resolves this ambiguity.
The naming convention is inconsistent: web_search and web_fetch use snake_case with verb_noun pattern, while resolve-library-id and query-docs use kebab-case. This mixed pattern (underscore vs hyphen) creates a lack of uniformity across the tool set, making it harder to anticipate tool names.
With only 4 tools, the set is tightly scoped for a web-bridge purpose: one search, one fetch, one library resolver, and one doc query tool. Each tool earns its place, and the count is well within the ideal 3-15 range.
The set covers complete workflows: general web search leads to web_fetch for content retrieval, and library resolution leads to query-docs for documentation. No obvious dead ends or missing operations are apparent for the stated hybrid purpose of bridging general web and library documentation access.