Recipes your AI agent can install
Signed webhook pipes to the services you already use. Your agent finds a recipe, you paste one credential on a secret page, and every delivery comes back with a receipt.
The credential never enters the model context: it lives in the FlurryPORT secret store, deliveries are signed server-side, and every send returns a receipt your agent can quote.
Start here
npx flurryport mcp
Point your agent at the FlurryPORT MCP server and ask it to search recipes. Works from AI clients that can run a local process (desktop apps and terminal agents); web-only chat clients cannot reach one.
Featured recipes
Let your AI add records to an Airtable table; the token stays server-side.
Create and update Azure DevOps work items in one batched pipe: priority, state, tags, and sprint included.
Query Azure DevOps work items with WIQL and read the matching ids back, without your AI ever holding the PAT.
Read fields for a batch of Azure DevOps work items by id: title, state, tags, priority, iteration.
Let your AI file Azure DevOps work items (bugs, tasks) the model never holds credentials for.
Domain seats draft one plan and check each other’s claims; rank can complete over an objection, and the objection stays on the record.
Turn captured webhooks into byte-exact test fixtures: real provider bytes, re-signed with a test secret, guarded so any reformat fails the build.
Convene a code-review room: one human chair, a coder seat, and a reviewer seat on a signed stream. Every commission closes with a verdict and a commit.
Browse by category
3 recipes
1 recipe
11 recipes
2 recipes
1 recipe
1 recipe
2 recipes
1 recipe
8 recipes
Popular destinations
Suites
A suite is a ladder of recipes for one service that share a setup and a signing key, so the second install is a paste, not a project.
File, query, read and manage Azure Boards work items from an AI agent, with the personal access token held server-side and never handed to the model.
4 recipes
File, search, read and update GitHub issues from an AI agent, with the fine-grained personal access token held server-side and never handed to the model.
3 recipes
Five recipes, one protocol family: your team's AIs coordinating over signed, ordered FlurryPORT streams.
5 recipes