IBM Agentic Tooling
As an AI Solutions Engineer at IBM, I build client-facing solutions and architect internal tooling to optimize our team’s operational workflows. My key contributions include:
• Engineeering end-to-end workflows bridging Mural, Bob, and Figma by developing a custom Mural MCP server alongside IBM’s internal Figma MCP.
• Automating cross-functional business tracking and client engagement pipelines within Monday.com.
01: Mural to Figma Workflow
I built an internal Agentic AI tool layer for IBM Bob, IBM’s generative task assistant, which integrates directly with Mural, a white boarding tool we use with clients, via the Model Context Protocol.
A problem I noticed is that during intense client workshops, critical requirements often get lost in translation with the team. I engineered this to act as a bridge, enabling Bob to dynamically read, synthesize, and structurally execute changes directly into Mural.
Here’s how it works:
+---------------------------+
| Client Workshop (Mural) |
+---------------------------+
|
| unstructured sticky notes, research, & requirements
v
+---------------------------+
| Custom Mural MCP Server |
+---------------------------+
|
| exposes canvas objects & spatial context via MCP
v
+---------------------------+
| IBM Bob |
| AI Task Assistant |
+---------------------------+
|
| synthesizes notes & generates structured UI/UX specs
v
+---------------------------+
| IBM Internal Figma MCP |
+---------------------------+
|
| executes layout mutations & generates templates
v
+---------------------------+
| Figma Wireframe Templates |
+---------------------------+
Sample Mural board
Using Custom Mural MCP to synthesize Mural board
After synthesizing project notes in Mural and routing them to IBM Bob, team members can leverage the internal Figma MCP to automatically generate structured design templates.
Figma MCP to generate designs
02: Monday.com Workflow
Engineered an automated Monday.com workflow that dynamically enriches board data from unstructured user inputs. When a project name or status update is modified, a webhook triggers a custom NodeJS server hosted on Railway, which processes the payload via the OpenAI API and populates the remaining board fields automatically.
Here’s how it works:
+------------------------------+
| monday.com Board |
| trigger: item updated |
+------------------------------+
|
| signs POST with JWT (MONDAY_SIGNING_SECRET)
| sends over HTTPS
v
+------------------------------+
| Custom Node.js Server |
| Railway — webhook handler |
+------------------------------+
|
| verifies JWT, extracts note text
v
+------------------------------+
| watsonx.ai |
| IBM Cloud infrastructure |
+------------------------------+
|
| parses & enriches note, returns structured fields
v
+------------------------------+
| monday.com GraphQL API |
| over HTTPS |
+------------------------------+
|
| updates board columns
v
+------------------------------+
| Board Updated |
+------------------------------+
Trigger 01: Updating the opportunity name
Trigger 02: Updating the opportunity updates