OpenClaw plugin

OpenClaw should use the same portable Skill.md file. Use these values to connect OpenClaw to Memex.

Open the skill

Use the same memex-agent-skill markdown in OpenClaw.

Get credentials

OpenClaw needs the same Memex API key as every other integration.

Required values

OpenClaw integrations need:

MEMEX_API_KEY

If your setup uses MCP directly, also keep:

MEMEX_MCP_URL=https://memex.garden/api/mcp

Environment variables

export MEMEX_API_KEY="YOUR_MEMEX_API_KEY"
export MEMEX_MCP_URL="https://memex.garden/api/mcp"

Config example

If your OpenClaw install supports env-backed per-skill settings, wire the Memex values into the skill entry:

{
    skills: {
        entries: {
            'memex-agent-skill': {
                enabled: true,
                apiKey: {
                    source: 'env',
                    provider: 'default',
                    id: 'MEMEX_API_KEY',
                },
                mcpUrl: {
                    source: 'env',
                    provider: 'default',
                    id: 'MEMEX_MCP_URL',
                },
            },
        },
    },
}

If your OpenClaw version uses different field names, keep the same underlying env vars and map them to your local schema.

Which Memex surface to call

If OpenClaw can speak MCP, point it at https://memex.garden/api/mcp.
If OpenClaw only issues HTTP requests, use the routes and parameter shapes from Available endpoints and send X-Api-Key: YOUR_MEMEX_API_KEY on each request.

Troubleshooting

Missing credentials: Authentication
Out of credits: Buy credits
Bad request shape: Available endpoints

General

API reference

Plugins

Open the skill

Get credentials

Required values

Environment variables

Config example

Which Memex surface to call

Troubleshooting

Open the skill

Get credentials

​Required values

​Environment variables

​Config example

​Which Memex surface to call

​Troubleshooting

Required values

Environment variables

Config example

Which Memex surface to call

Troubleshooting