Skip to main content
Glama
BACH-AI-Tools

Recipe By Api Ninjas MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Recipe By Api Ninjas MCP Server

English | 简体中文 | 繁體中文

用于访问 Recipe By Api Ninjas API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-recipe_by_api_ninjas）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: cook-mcp

简介

这是一个 MCP 服务器，用于访问 Recipe By Api Ninjas API。

  • PyPI 包名: bach-recipe_by_api_ninjas

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-recipe_by_api_ninjas

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-recipe_by_api_ninjas bach_recipe_by_api_ninjas

# 或指定版本
uvx --from bach-recipe_by_api_ninjas@latest bach_recipe_by_api_ninjas

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-recipe_by_api_ninjas

# 运行（命令名使用下划线）
bach_recipe_by_api_ninjas

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-recipe_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-recipe_by_api_ninjas", "bach_recipe_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-recipe_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-recipe_by_api_ninjas", "bach_recipe_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

v1recipe

Get a list of recipes for a given search query. Returns at most 10 results. To access more than the first 10 results, use the offset parameter to offset results in multiple API calls.

端点: GET /v1/recipe

参数:

  • query (string) 必需: query text to search.

  • offset (string): number of results to offset for pagination.

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
v1recipeA

Get a list of recipes for a given search query. Returns at most 10 results. To access more than the first 10 results, use the offset parameter to offset results in multiple API calls.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesquery text to search.
offsetNonumber of results to offset for pagination.

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool returns at most 10 results and supports pagination via offset, which are key behavioral traits. However, it does not mention error behavior, rate limits, or whether the operation is read-only (though 'Get a list' implies idempotence). The transparency is good but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loading the core purpose in the first sentence and pagination guidance in the second. There is no redundant or unnecessary text. Every sentence serves a clear function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 parameters, no output schema, no siblings), the description covers the essential behavior: search, result limit, and pagination. It does not explain the structure of returned recipes, but an output schema is absent and may not be critical for a list tool. The description feels adequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for both parameters, so the schema already documents parameter meaning. The description adds value by explaining the pagination behavior ('Returns at most 10 results. To access more... use the offset parameter'), which gives practical context beyond the schema. This justifies a score above the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get a list of recipes'), the resource ('recipes'), and the trigger ('for a given search query'). It also specifies a key constraint (maximum 10 results) and pagination behavior, making the purpose unambiguous. No sibling tools exist, so differentiation is not required.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use the offset parameter for pagination ('To access more than the first 10 results, use the offset parameter'). It implies the tool is for basic search queries but does not specify when not to use it or list alternatives. Since there are no sibling tools, this is adequate but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedv1recipe
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is uniquely defined.

Naming Consistency5/5

There is only one tool, so naming consistency is trivially perfect. The name 'v1recipe' is a single, clear identifier without mixed conventions.

Tool Count2/5

Having only one tool is too few for the apparent scope of a recipe server. Typical recipe APIs require multiple endpoints (search, get by ID, etc.), and a single tool feels thin and insufficient.

Completeness2/5

The server only provides a search/list function. Missing essential operations like getting a specific recipe, creating, updating, or deleting recipes. This is a significant gap for a recipe management server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • cook-mcp

    HZZY2019
    F
    license
    A
    quality
    D
    maintenance
    MCP server that provides cooking recipe lookup, classification, and weekly meal planning based on dietary restrictions and allergies.
    5
    -

  • Meals MCP Server

    pristley
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server for discovering and retrieving meal recipes from TheMealDB API, enabling search, random meals, category/ingredient filtering, and full recipe details.
    -

  • recipe-mcp

    valetdotdev
    A
    license
    A
    quality
    D
    maintenance
    An MCP server for AI-powered recipe generation and transformation, enabling users to create custom recipes from natural language descriptions and modify existing ones to meet dietary and nutritional goals.
    2
    69
    1
    MIT