MCP Connector

Connect IBM wxflows to Data Sources

IBM wxflows MCP Server tutorial deploys watsonx.ai Flows Engine tools like google_books and wikipedia to any MCP client.

Works with ibm

84
Spark score
out of 100
Updated Sep 2025
Source checked Sep 15, 2026
Version 0.22.0
Models
universal

Add to Favorites

Why it matters

Integrate IBM's wxflows platform with various data sources for tool creation, testing, and deployment. Facilitates seamless communication and debugging for complex data workflows.

Outcomes

What it gets done

01

Connect wxflows to diverse data sources.

02

Enable debugging of MCP server communication.

03

Support the creation and deployment of tools.

04

Facilitate ETL synchronization for data workflows.

Source

Get it from source

Spark does not host a copy of it.

Open source

Reports

Agent outcome reports

No reports yet

Overview

IBM wxflows MCP Server

IBM wxflows MCP Server is a tutorial project pairing the MCP TypeScript SDK with the wxflows SDK to serve IBM watsonx.ai Flows Engine tools - google_books and wikipedia by default - to any MCP client. Use it as a reference when building an MCP server backed by watsonx.ai Flows Engine tools; it needs a wxflows account and a deployed Flows Engine endpoint.

What it does

IBM wxflows MCP Server is a working example that pairs the MCP TypeScript SDK with the wxflows SDK to expose watsonx.ai Flows Engine tools to any MCP client. The example project pre-configures two Flows Engine tools - google_books (searching books, exposing books and book fields) and wikipedia (searching pages, exposing search and page fields) - and deploys them behind a single Flows Engine endpoint, api/mcp-example, which the MCP server then serves to a client such as Claude Desktop.

When to use - and when NOT to

Use it as a starting point when you want an MCP server backed by IBM's watsonx.ai Flows Engine rather than hand-written tool code - the tutorial shows exactly how to deploy Flows Engine tools and wire them into an MCP client. It requires a wxflows account (sign-up plus CLI authentication) and a deployed Flows Engine endpoint, so it is not a zero-setup drop-in; skip it if you just need a generic Wikipedia or Google Books lookup without also adopting the Flows Engine tool-deployment model.

Capabilities

Out of the box the example exposes google_books and wikipedia as callable tools through the Flows Engine endpoint. Because the underlying wxflows SDK is a general tool-import layer, the same deploy-then-serve pattern extends to importing tools from databases, NoSQL stores, REST APIs, or GraphQL APIs, not just the two documented examples - the project's own tools guide covers adding further tool sources.

How to install

Clone the repo and open the example directory (git clone https://github.com/IBM/wxflows.git, then cd examples/mcp/javascript), sign up for a wxflows account, and install and authenticate the Node.js CLI. From the wxflows subdirectory, run wxflows deploy to deploy the pre-configured google_books and wikipedia tools to the api/mcp-example endpoint. Copy .env.sample to .env and fill in your credentials, run npm i to install dependencies (including @wxflows/sdk), then npm run build to build the server. Point an MCP client at the built server, for example in Claude Desktop's config:

{
  "mcpServers": {
    "wxflows-server": {
      "command": "node",
      "args": ["/path/to/wxflows-server/build/index.js"],
      "env": {
        "WXFLOWS_APIKEY": "YOUR_WXFLOWS_APIKEY",
        "WXFLOWS_ENDPOINT": "YOUR_WXFLOWS_ENDPOINT"
      }
    }
  }
}

Because MCP servers communicate over stdio, debugging can be awkward; the project recommends running npm run inspector, which starts the MCP Inspector and prints a URL you open in your browser to see requests and responses between the client and the server. The project also points to a Discord channel for questions or feedback while working through the setup.

Who it's for

Developers already using or evaluating IBM watsonx.ai Flows Engine who want a concrete, working reference for exposing Flows Engine tools through MCP, rather than building the client-to-Flows-Engine bridge from scratch. The example is built on the MCP TypeScript SDK and Node.js tooling (npm, a build step), so it fits teams working in that stack.

Source README

Using watsonx.ai Flows Engine with Model Context Protocol (MCP)

Here's a step-by-step tutorial for setting up and deploying a project with wxflows, including installing necessary tools, deploying the app, and running it locally.

This example consists of the following pieces:

  • MCP TypeScript SDK (mcp server)
  • wxflows SDK (tools)

You can use any of the supported MCP clients.

This guide will walk you through installing the wxflows CLI, initializing and deploying a project, and running the application locally. We’ll use google_books and wikipedia tools as examples for tool calling with wxflows.

Before you start

Clone this repository and open the right directory:

git clone https://github.com/IBM/wxflows.git
cd examples/mcp/javascript

Step 1: Set up wxflows

Before you can start building AI applications using watsonx.ai Flows Engine:

  1. Sign up for a free account
  2. Download & install the Node.js CLI
  3. Authenticate your account

Step 2: Deploy a Flows Engine project

Move into the wxflows directory:

cd wxflows

There's already a wxflows project for you set up this repository with the following values:

  • Defines an endpoint api/mcp-example for the project.
  • Imports google_books tool with a description for searching books and specifying fields books|book.
  • Imports wikipedia tool with a description for Wikipedia searches and specifying fields search|page.

You can deploy this tool configuration to a Flows Engine endpoint by running:

wxflows deploy

This command deploys the endpoint and tools defined, these will be used by the wxflows SDK in your application.

Step 3: Set Up Environment Variables

From the project’s root directory copy the sample environment file to create your .env file:

cp .env.sample .env

Edit the .env file and add your credentials, such as API keys and other required environment variables. Ensure the credentials are correct to allow the tools to authenticate and interact with external services.

Step 4: Install Dependencies in the Application

To run the application you need to install the necessary dependencies:

npm i

This command installs all required packages, including the @wxflows/sdk package and any dependencies specified in the project.

Step 5: Build the MCP server

Build the server by running:

npm run build

Step 6: Use in a MCP client

Finally, you can use the MCP server in a client. To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "wxflows-server": {
      "command": "node",
      "args": ["/path/to/wxflows-server/build/index.js"],
      "env": {
        "WXFLOWS_APIKEY": "YOUR_WXFLOWS_APIKEY",
        "WXFLOWS_ENDPOINT": "YOUR_WXFLOWS_ENDPOINT"
      }
    }
  }
}

You can now open Claude Desktop and should be seeing the tools from the wxflows-server listed. You can now test the google_books and wikipedia tools through Claude Desktop.

Summary

You’ve now successfully set up, deployed, and run a wxflows project with google_books and wikipedia tools. This setup provides a flexible environment to leverage external tools for data retrieval, allowing you to further build and expand your app with wxflows. See the instructions in tools to add more tools or create your own tools from Databases, NoSQL, REST or GraphQL APIs.

Installation

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "weather-server": {
      "command": "/path/to/weather-server/build/index.js"
    }
  }
}

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.