OpenClaw

Teapplix MCP can be linked to OpenClaw by installing mcporter package. It is beyond the scope of this document to describe how to install and setup OpenClaw. A few hints we have is that it is lot easier to install latest nodejs globally on your machine, and also openclaw globally.

The tool to call Teapplix from openclaw is called mcporter. To install on your machine, type:

npm install -g mcporter

You also have to go to OpenClaw skills marketplace, to download and install the official mcporter SKILL. You should verify, that in your BUILD-IN skills, mcporter skill is enabled.

After mcporter is installed, to authorize mcporter to access your Teapplix account, you have 2 ways:

Config File

You can store your Teapplix REST API key on your local computer where openclaw runs. To do that edit .mcporter/mcporter.json (note, since openclaw can read this file, it is perfectly capable of disclosing this information if you do not lock down your install correctly. We recommend you test with this method for simplicity, and once everything is working, you should delete this and switch to oauth method below):

{
  "servers": {
    "teapplix": {
      "url": "https://api.teapplix.com/mcp",
      "headers": {
        "X-Teapplix-Api-Token": "your_api_token_here"
      }
    }
  }
}

Oauth

mcporter has a bug that the last step of oauth will give an error, but it still successfully link and authorize Teapplix. This is a more secure way. With Oauth, no API key is stored on your machine where you run OpenClaw.

To setup oauth link, on command line type:

$ mcporter auth teapplix --reset
[mcporter] OAuth authorization required for 'teapplix'. Waiting for browser approval…
[mcporter] Failed to authorize 'teapplix': SSE error: Non-200 status code (501)
Error: Failed to authorize 'teapplix': SSE error: Non-200 status code (501)
at handleAuth (file:///home/xudong/node_modules/mcporter/dist/cli.js:465:19)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async runCli (file:///home/xudong/node_modules/mcporter/dist/cli.js:152:13)
at async main (file:///home/xudong/node_modules/mcporter/dist/cli.js:201:5)

You will be prompted on a browser to login to Teapplix, and grant permission. After that, mcporter prints the 501 error message, as there is a bug in the program. But the link actually successfully finished. You can verify as there should be a file under .mcporter/credentials.json created.

Testing mcporter

After either of the above 2 methods to authorize mcporter to talk to Teapplix, type the following command to test:

mcporter list teapplix

You will find that it print out all the tools and how to call them, without any error messages.

Setting up your Agents.md

To automatically load each session with Teapplix API information, so the agent can call Teapplix API for you, go to your .openclaw/workspace folder, and edit your Agents.md file. This control your main chat session, you will find a section in the file like this:

##Session Startup

Before doing anything else:

1. Read SOUL.md — this is who you are
2. Read USER.md — this is who you're helping
3. Read memory/YYYY-MM-DD.md (today + yesterday) for recent context
4. If in MAIN SESSION (direct chat with your human): Also read MEMORY.md
5. Run mcporter list teapplix, report any error via chat to user.

You add line 5. exactly as it is to Agents.md to make it load Teapplix API definition each time session starts.