Edamam Recipe Search (BYOK) — connector documentation

MCP endpoint: https://byok-edamam.connectorbay.com/mcp
REST API: POST https://byok-edamam.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-edamam.connectorbay.com/openapi.json
Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
Authentication: your own Edamam application key (app_key), sent in the X-Upstream-Key header and the application ID (app_id) in X-Upstream-Key-2 of every request (never stored, logged or cached)
Health: https://byok-edamam.connectorbay.com/health · Tool schemas: https://byok-edamam.connectorbay.com/tools.json
Publisher: Unify Dynamics LLC · connectorbay.com/byok-edamam · agent@connectorbay.com

What Edamam Recipe Search (BYOK) is for

Edamam Recipe Search (BYOK) lets an AI assistant read your own Edamam data through the Edamam API with a key you supply (application key (app_key)). Read-only: 5 tools (search_recipes, search_recipes_by_label, get_random_recipes, get_recipe, get_recipes_by_uri). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.edamam.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Edamam. Edamam and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

"Find chicken recipes under 500 calories that take 30 minutes or less"
"Find vegan Indian dinner recipes"
"Suggest some random lunch recipes"
"Show me the details of this Edamam recipe"
"Look up the recipe with uri http://www.edamam.com/ontologies/edamam.owl#recipe_9b5945e03f05acbf9d69625138385408"

What it does

search_recipes: Search recipes by keyword with optional limits on calories per serving, total minutes and number of ingredients. Returns one page of results (the provider's page size); the follow-up link of the provider carries the key, so it is not returned.
search_recipes_by_label: Search recipes filtered by one diet, health label, cuisine, meal type or dish type, with optional search text. Returns one page of results (the provider's page size); the follow-up link of the provider carries the key, so it is not returned.
get_random_recipes: Get a random selection of up to 20 recipes that match optional search text, diet or meal type.
get_recipe: Get one recipe by its id (the last part of a recipe uri, for example the 32-character code). Returns the recipe's title, source link, servings, calories, labels and ingredient lines; the cooking steps are on the source site.
get_recipes_by_uri: Get one recipe by its full Edamam recipe uri, as returned in the 'uri' field of a search result. Returns the recipe's title, source link, servings, calories, labels and ingredient lines; the cooking steps are on the source site.

BYOK key

You bring your own Edamam application key (app_key) (https://developer.edamam.com/admin/applications). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.edamam.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

https://developer.edamam.com/edamam-docs-recipe-api (the API this connector calls, with a BYOK key)

Live from the Edamam API (api.edamam.com) with a BYOK key; documentation: https://developer.edamam.com/edamam-docs-recipe-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Edamam. Edamam and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Edamam account.

Built for: Worldwide. Languages: English.