Metaso Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METASO_API_KEY | Yes | Metaso API key / 秘塔 API 密钥 | |
| METASO_TIMEOUT | No | Timeout in milliseconds for API requests | 60000 |
| METASO_BASE_URL | No | Base URL for Metaso API | https://metaso.cn/api/v1 |
| METASO_DEFAULT_SEARCH_SIZE | No | Default number of search results (1-100) | 10 |
| METASO_DEFAULT_SEARCH_SCOPE | No | Default search scope: webpage, document, paper, image, video, podcast | |
| METASO_DEFAULT_READER_FORMAT | No | Reader output format: markdown or json | markdown |
| METASO_DEFAULT_CONCISE_SNIPPET | No | Whether to use concise snippets (true/false) | |
| METASO_DEFAULT_INCLUDE_SUMMARY | No | Whether to include summary in results (true/false) | |
| METASO_DEFAULT_INCLUDE_RAW_CONTENT | No | Whether to include raw content (true/false) |
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 |
|---|---|
| metaso_searchA | 使用秘塔AI搜索进行多维度搜索。 支持的搜索范围 (scope):
特色功能:
|
| metaso_readerA | 读取指定URL的网页内容并转换为结构化格式。 支持的输出格式:
适用场景:
|
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 2 tools
The two tools have clearly distinct purposes: one performs searches across multiple scopes, and the other reads and converts a specific URL. There is no ambiguity between them.
Both tools follow the same 'metaso_' prefix and use underscore-separated lowercase words. The naming pattern is consistent and predictable.
With only two tools, the set is at the low end of acceptable. For a search-and-read server, the minimalism is defensible, but it feels slightly thin compared to a typical well-scoped server.
The search tool covers diverse scopes (web, documents, papers, images, videos, podcasts) and the reader handles URL content extraction. Together they cover the core search-and-read pipeline, though advanced features like search history or saved results are missing.