Skip to main content
This guide gets your OpenClaw agent connected to Shuriken in about 2 minutes. Once set up, your agent can monitor your alpha groups, research tokens, check your portfolio, and execute trades - all through WhatsApp, Telegram, Discord, or the built-in Control UI. Time required: About 2 minutes.

Prerequisites

  • OpenClaw installed and running (openclaw gateway status should show it’s active)
  • A Shuriken Agent Key (create one here if you haven’t already)

Step-by-step setup

1

Copy your Agent Key

If you just created your key, copy it from the setup screen. It starts with sk_.If you already closed that screen, you’ll need to create a new key - keys are only shown once.
2

Open the config file

OpenClaw stores its config in a JSON5 file called openclaw.json.Option A: Use the CLI (recommended)
Option B: Use the Control UIOpen http://127.0.0.1:18789 in your browser and go to the Config tab.Option C: Edit the file directly
3

Add the Shuriken MCP server

Add the following mcpServers block to your openclaw.json. Replace YOUR_AGENT_KEY with the key you copied in step 1.If you don’t have any MCP servers yet, add this to your config:
openclaw.json
If you already have MCP servers, add the shuriken block inside the existing mcpServers object:
openclaw.json
OpenClaw uses JSON5 format, so you don’t need to quote keys or worry about trailing commas. But standard JSON also works.
4

Save and reload

OpenClaw watches the config file and applies changes automatically - no restart needed in most cases.If the tools don’t appear, restart the gateway:
5

Verify the connection

Open the Control UI at http://127.0.0.1:18789 or message your agent through any connected channel (WhatsApp, Telegram, Discord, etc.) and try:
If you see results from Shuriken, you’re all set. Your OpenClaw agent is now connected.

Troubleshooting

OpenClaw strictly validates its config. If the gateway won’t start after your changes:
This will diagnose and suggest repairs. Common issues: unknown keys, malformed types, or invalid JSON5 syntax.
  • Make sure the mcpServers block is at the root level of your config (not nested inside another section)
  • Check that your Agent Key is correct (starts with sk_)
  • Make sure you included the AgentKey prefix before the key (with a space)
  • Try restarting the gateway: openclaw gateway restart
  • Double-check your Agent Key hasn’t been revoked on the Agent Keys dashboard
  • Make sure the key has the permissions needed for the tool you’re trying to use (see Permissions)