OpenClaw

Connect

OpenClaw configures MCP servers in ~/.openclaw/openclaw.json. Add Nimply as a remote streamable-HTTP server with your API key:

{
  "mcp": {
    "servers": {
      "nimply": {
        "url": "https://mcp.nimply.io/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer nim_live_YOUR_KEY"
        }
      }
    }
  }
}

Or from the CLI:

openclaw mcp set nimply '{
  "url": "https://mcp.nimply.io/mcp",
  "transport": "streamable-http",
  "headers": {"Authorization": "Bearer nim_live_YOUR_KEY"}
}'

Create the key in Nimply → Settings → Developers. Verify the connection:

openclaw mcp doctor nimply --probe
openclaw mcp status --verbose

Uploading generated media

OpenClaw can execute shell commands, so it can push locally generated files (e.g. AI-generated images) straight into your media library without hosting them anywhere: it calls create_media_upload, PUTs the raw bytes to the returned presigned URL, then calls complete_media_upload. Just ask it to upload the file — no public URL needed.

Try it

• "Use nimply to list my channels and queue this image as an Instagram post in the next free slot."
• "Every Monday, draft a week of posts from my notes and send them for approval in nimply."

Troubleshooting

• 401 Unauthorized — the header must be exactly Bearer nim_live_...; regenerate the key in Settings → Developers if it was revoked.
• Server not listed — run openclaw mcp doctor nimply --probe and check the gateway logs; older OpenClaw versions need an update for streamable-HTTP support.
• Key in a committed config — openclaw.json is plain text; keep it out of dotfile repos, or store the token in an environment variable if your OpenClaw version supports header expansion.