Click on "Install 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., "@Exercises By Api Ninjas MCP Server Show me intermediate strength exercises for chest"
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.
用于访问 Exercises By Api Ninjas API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-exercises_by_api_ninjas）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: Celebrity By Api Ninjas
这是一个 MCP 服务器，用于访问 Exercises By Api Ninjas API。
PyPI 包名: bach-exercises_by_api_ninjas
版本: 1.0.0
传输协议: stdio
pip install bach-exercises_by_api_ninjaspip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-exercises_by_api_ninjas bach_exercises_by_api_ninjas
# 或指定版本
uvx --from bach-exercises_by_api_ninjas@latest bach_exercises_by_api_ninjaspython server.py# 安装
pip install bach-exercises_by_api_ninjas
# 运行（命令名使用下划线）
bach_exercises_by_api_ninjas此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-exercises_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-exercises_by_api_ninjas", "bach_exercises_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-exercises_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-exercises_by_api_ninjas", "bach_exercises_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
v1exercisesAPI Ninjas Exercises API endpoint. Returns up to 10 exercises that satisfy the given parameters.
端点: GET /v1/exercises
参数:
name (string): name of exercise. This value can be partial (e.g. press will match Dumbbell Bench Press)
type (string): exercise type. Possible values are: cardio olympic_weightlifting plyometrics powerlifting strength stretching strongman
muscle (string): muscle group targeted by the exercise. Possible values are: abdominals abductors adductors biceps calves chest forearms glutes hamstrings lats lower_back middle_back neck quadriceps traps triceps
difficulty (string): difficulty level of the exercise. Possible values are: beginner intermediate expert
offset (number): number of results to offset for pagination. Default is 0.
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
API Ninjas Exercises API endpoint. Returns up to 10 exercises that satisfy the given parameters.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | name of exercise. This value can be partial (e.g. press will match Dumbbell Bench Press) | |
| type | No | exercise type. Possible values are: cardio olympic_weightlifting plyometrics powerlifting strength stretching strongman | |
| muscle | No | muscle group targeted by the exercise. Possible values are: abdominals abductors adductors biceps calves chest forearms glutes hamstrings lats lower_back middle_back neck quadriceps traps triceps | |
| difficulty | No | difficulty level of the exercise. Possible values are: beginner intermediate expert | |
| offset | No | number of results to offset for pagination. Default is 0. | 0 |
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 mentions the tool returns up to 10 exercises and uses parameters, but does not cover important aspects like rate limits, authentication needs, error handling, or response format. This leaves significant gaps in understanding the tool's behavior.
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 a single, efficient sentence that front-loads key information: it identifies the API, states the action, and notes the result limit. There is no wasted language, making it highly concise and well-structured for quick understanding.
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?
Given the tool's moderate complexity (5 optional parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and result limit, but lacks details on behavioral traits, usage context, and output format. This makes it minimally viable but with clear gaps for effective agent use.
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 description adds minimal value beyond the input schema, which has 100% coverage and detailed descriptions for all 5 parameters. It implies that parameters filter the results, but does not explain interactions between parameters or provide additional context. With high schema coverage, the baseline score of 3 is appropriate.
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 clearly states the tool's purpose: it returns up to 10 exercises based on given parameters. It specifies the verb ('Returns'), resource ('exercises'), and scope ('up to 10'), but since there are no sibling tools, it cannot differentiate from alternatives. This makes it clear but not maximally specific.
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?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It mentions that it returns exercises based on parameters, but this is implied usage rather than explicit instructions. With no sibling tools, the lack of comparative guidance is less critical but still a gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare it against for patterns or conventions.
One tool is too few for a server with a domain like exercises, which typically requires operations like searching, filtering, or retrieving details. This minimal set limits functionality and feels incomplete for the scope.
The server covers only a basic query function (v1exercises), lacking essential operations such as getting exercise details by ID, creating custom exercises, or managing user-specific data. This represents significant gaps for a comprehensive exercise-related service.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Query workouts, browse exercises, and explore fitness data from BearTrail
Log workouts and meals by telling your AI. 873 exercises, muscle diagrams, food lookup.
Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key.
API Ninjas MCP — wraps the multi-endpoint API Ninjas data API (api-ninjas.com)
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/exercises_by_api_ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server