Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Helpter Notebook to Understand MCP Tools and Agents

Closed
  • Is something wrong?
#452 6 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@MannXo is already working on this.

Since Jul 27, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, jupyter-notebook, python
Domain
ai, documentation, embedded-iot

Research direction

Start by reading the repository documentation for the local Docker and data setup, then identify the IoT MCP server and MCPHub workflow entry points. Create a supporting Colab notebook that follows the documented setup, demonstrates site, asset, data, and plotting exploration, and covers all IoT server tools through Tool Universe. Done means a first-time user or KDD tutorial participant can run the notebook successfully from the stated prerequisites.

Written by the indexing model from the issue text.

Description

good first issue stale

AssetOpsBench comes with MCP Server for Industrial AI. This issue is created to seek help from the community in providing a supporting document (preferably created manually) to assist first-time users or, say, our KDD tutorial participants.

We are planning to release a series of Colab Notebook that are easy for any one to experience the MCP Tools for each server. We like to start with IoT.

  • A notebook should assume we have setup a docker locally and uploaded a data as per as document.
  • Now we are try to use MCP tools to explore all site, assets, some data, plot and etc.
  • Ideally a single notebook shoould cover all the tools
  • use MCPHub (workflow) to run tool Tool Universe.

If you interested to take up the issue, please drop a note as comment.

Dominant language
Python
Stars
2.3k
Forks
332
Avg merge
8h 40m
Merged PRs (30d)
33

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IBM/AssetOpsBench

All issues in IBM/AssetOpsBench

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.