Blocks
MCP Prompt
Create and manage Model Context Protocol prompts
Create and manage prompts for MCP servers. Prompts are reusable templates for LLM interactions.
Block Preview
MCP Prompt
Create and manage Model Context Protocol prompts
Usage
- Add the block to your workflow and connect it to the upstream step.
- Configure any required credentials or tokens in the inputs.
- Fill in required inputs and optional parameters for the run.
- Run a test execution, inspect outputs, and iterate before deploying.
- Deploy the mcp_prompt block with monitoring enabled in production.
Inputs (UI)
Operation
dropdownLayout: full
Options: Create Prompt, Get Prompt, Update Prompt, Delete Prompt
Prompt Name
short-inputPlaceholder: my-prompt
Layout: half
Condition: operation = ["create_prompt","get_prompt","update_prompt","delete_prompt"]
Prompt Description
short-inputPlaceholder: Description of what the prompt does
Layout: full
Condition: operation = ["create_prompt","update_prompt"]
Parameter Schema (JSON)
codePlaceholder: { "param1": {"type": "string", "description": "First parameter"}, "param2": {"type": "string", "description": "Second parameter"} }
Layout: full
Condition: operation = ["create_prompt","update_prompt"]
Prompt Template (JavaScript)
codePlaceholder: ({ param1, param2 }) => ({ messages: [ { role: "user", content: { type: "text", text: `Process this: ${param1} and ${param2}` } } ] })
Layout: full
Condition: operation = ["create_prompt","update_prompt"]
Prompt Arguments (JSON)
codePlaceholder: { "param1": "value1", "param2": "value2" }
Layout: full
Condition: operation = "get_prompt"
Server URL
short-inputPlaceholder: http://localhost:3000/mcp or stdio://path/to/server.js
Layout: full
Timeout (ms)
short-inputPlaceholder: 30000
Layout: half
Inputs (API)
operation
stringRequired
serverUrl
stringRequired
promptName
stringOptional
promptDescription
stringOptional
paramSchema
jsonOptional
promptTemplate
stringOptional
promptArguments
jsonOptional
timeout
numberOptional
Outputs
Primary response type:
{
"success": "boolean",
"messages": "json",
"error": "string"
}