Recipe Generator Skill
The tool
Let your agent cook up recipes. Call it as an MCP tool to return full recipes with ingredients, steps and timings from a dish name.
Once your client is connected to the VerveKit MCP server, this appears in its tool list as RecipeGeneratorSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "RecipeGeneratorSkill",
"arguments": {
"name": "chicken fajitas"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about chicken fajitas in the terms this source covers is enough for it to reach for RecipeGeneratorSkill on its own.
Connecting
One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.
{
"mcpServers": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.
| Argument | Type | Example | Description |
|---|---|---|---|
nameRequired | string | chicken fajitas | The name or description of the recipe you want to generate |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"name": "Chicken Fajitas",
"description": "A flavorful and easy-to-make dish with marinated chicken, bell peppers, and onions, served with warm tortillas.",
"ingredients": [
"1.5 pounds boneless, skinless chicken breasts, sliced",
"1 red bell pepper, sliced",
"1 green bell pepper, sliced",
"1 large onion, sliced",
"2 tablespoons olive oil",
"1 packet (1 ounce) fajita seasoning",
"1/2 cup water",
"12 flour tortillas",
"Optional toppings: sour cream, guacamole, salsa, shredded cheese"
],
"instructions": "1. In a bowl, combine chicken with fajita seasoning and water. Marinate for at least 15 minutes.\n2. Heat olive oil in a large skillet or cast-iron pan over medium-high heat.\n3. Add the chicken and cook until browned and cooked through, about 5-7 minutes.\n4. Add bell peppers and onions to the skillet. Cook until softened, about 5-7 minutes.\n5. Warm tortillas according to package instructions.\n6. Serve chicken and vegetables in warm tortillas with desired toppings.",
"prep_time": "15 minutes",
"cook_time": "20 minutes",
"servings": 4
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
name | string | Chicken Fajitas | The name of the generated recipe dish |
description | string | A flavorful and easy-to-make dish with marinated chicken, bell peppers, and onions, served with warm tortillas. | Detailed description of the recipe including flavor profile and preparation method |
ingredients | array | ["1.5 pounds boneless, skinless chicken breasts, sliced","1 red bell pepper, sliced","1 green bell pepper, sliced"] | List of ingredients with quantities required for the recipe |
instructions | string | 1. In a bowl, combine chicken with fajita seasoning and water. Marinate for at least 15 minutes.
2. Heat olive oil in a large skillet or cast-iron pan over medium-high heat.
3. Add the chicken and cook until browned and cooked through, about 5-7 minutes.
4. Add bell peppers and onions to the skillet. Cook until softened, about 5-7 minutes.
5. Warm tortillas according to package instructions.
6. Serve chicken and vegetables in warm tortillas with desired toppings. | Step-by-step cooking instructions for preparing the recipe |
prep_time | string | 15 minutes | Time required to prepare ingredients before cooking begins |
cook_time | string | 20 minutes | Time required to cook the recipe from start to finish |
servings | number | 4 | Number of people the recipe serves |
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This skill isn't part of VerveKit. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use Recipe Generator Skill
Set up Recipe Generator Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Frequently asked questions
Do I have to tell the agent to use RecipeGeneratorSkill?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.