Provides access to the Similar Words API via the RapidAPI platform, enabling tools to find similar words and related linguistic information.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Similar Words MCP Server find words similar to 'innovation'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
用于访问 Similar Words API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-similar_words）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: LangSearch MCP Server
这是一个 MCP 服务器，用于访问 Similar Words API。
PyPI 包名: bach-similar_words
版本: 1.0.0
传输协议: stdio
pip install bach-similar_wordspip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-similar_words bach_similar_words
# 或指定版本
uvx --from bach-similar_words@latest bach_similar_wordspython server.py# 安装
pip install bach-similar_words
# 运行（命令名使用下划线）
bach_similar_words此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-similar_words": {
"command": "uvx",
"args": ["--from", "bach-similar_words", "bach_similar_words"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-similar_words": {
"command": "uvx",
"args": ["--from", "bach-similar_words", "bach_similar_words"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
api_endpoint请根据 RapidAPI 页面手动添加端点信息
端点: GET /endpoint
参数:
param (string): 参数
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
请根据 RapidAPI 页面手动添加端点信息
| Name | Required | Description | Default |
|---|---|---|---|
| param | No | 参数 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention any side effects, permissions, persistence, reversibility, or return behavior. For a tool that 'adds' information, there is no indication of what changes occur or what the output looks like.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (one sentence) and front-loaded, but it is under-specified. It earns its place only slightly by mentioning RapidAPI as a source, yet the brevity does not compensate for the lack of meaningful content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one optional parameter and no output schema, the description is extremely incomplete. It fails to explain the tool's purpose, how the parameter relates to the endpoint information, what the expected behavior is, or what the user should observe after invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one optional parameter 'param' with a description '参数' (parameter), which is tautological and provides no real semantics. The tool description adds nothing about how to use the parameter or what values it expects. Although schema coverage is 100%, the content is useless, and the description does not compensate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Please manually add endpoint information based on the RapidAPI page' uses a specific verb ('add') but the resource ('endpoint information') is vague and the phrase reads more like an instruction to a human than a functional tool description. It does not clearly define what the tool actually does or what constitutes endpoint information, making it barely rise above a tautology.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives. The phrase 'based on the RapidAPI page' implies a context but does not explicitly state usage scenarios, prerequisites, or exclusions. No alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0api_endpointScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'api_endpoint' stands alone with a distinct purpose of adding endpoint information from RapidAPI pages.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'api_endpoint' uses a clear and descriptive snake_case format, which sets a good precedent if more tools were added.
A single tool is too few for most server purposes, as it severely limits functionality and suggests the server is underdeveloped. For a server named 'Similar Words MCP Server', one might expect multiple tools for tasks like finding synonyms, antonyms, or word comparisons, making this count inappropriate.
The tool set is severely incomplete for the inferred domain of word similarity. With only one tool for adding endpoint information, there are no tools for core operations like querying similar words, comparing terms, or managing word lists, leaving significant gaps that will cause agent failures.
The Needle MCP server enables semantic search on documents stored in files like PDFs, DOCX, and XLSX by connecting AI applications to external data sources. It provides capabilities to create and manage document collections, perform natural language searches on stored content, and retrieve relevant information without requiring exact keyword matches.
Words MCP — wraps Datamuse API (free, no auth required)
