Skip to content

Install Steve Memo

Create an API key on the Agents page, add the MCP server to your host, then save the skill. Each host reads the key from its own env var.

Create a key. Access is invite-only during early access. No account yet? Join the waitlist.

Cursor

One click adds the MCP server. Cursor reads the key from ${env:STEVE_MEMO_CURSOR_API_KEY}.

Cursor MCP config~/.cursor/mcp.json

{
  "mcpServers": {
    "steve-memo": {
      "url": "https://mcp.steve-memo.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:STEVE_MEMO_CURSOR_API_KEY}"
      }
    }
  }
}

Claude Code

Run the CLI command, or paste the JSON into ~/.claude.json. Claude Code reads the key from ${STEVE_MEMO_CLAUDE_API_KEY}. Capture hooks come from the repo plugin on a disposable host. There is no published /plugin.

Claude MCP CLI

claude mcp add --transport http steve-memo \
  https://mcp.steve-memo.com/mcp \
  --header 'Authorization: Bearer ${STEVE_MEMO_CLAUDE_API_KEY}'

Claude MCP config~/.claude.json

{
  "mcpServers": {
    "steve-memo": {
      "type": "http",
      "url": "https://mcp.steve-memo.com/mcp",
      "headers": {
        "Authorization": "Bearer ${STEVE_MEMO_CLAUDE_API_KEY}"
      }
    }
  }
}

Claude Desktop

Claude Desktop cannot send an API key header to a remote server, so this config runs the open-source mcp-remote bridge through npx (needs Node.js 18 or later). Open Settings, Developer, Edit Config, paste it, replace ak_… with your key, and restart Claude Desktop. This recipe is not yet verified.

Claude Desktop MCP configclaude_desktop_config.json

{
  "mcpServers": {
    "steve-memo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.steve-memo.com/mcp",
        "--header",
        "Authorization:${STEVE_MEMO_AUTH_HEADER}"
      ],
      "env": {
        "STEVE_MEMO_AUTH_HEADER": "Bearer ak_…"
      }
    }
  }
}

Grok CLI

Add this block to ~/.grok/config.toml. Grok CLI reads the key from ${STEVE_MEMO_GROK_API_KEY}. For Grok Bot, see below.

Grok CLI MCP config~/.grok/config.toml

[mcp_servers.steve-memo]
url = "https://mcp.steve-memo.com/mcp"
headers = { "Authorization" = "Bearer ${STEVE_MEMO_GROK_API_KEY}" }

Grok Bot

Grok Bot does not expand env vars, so the Cursor snippet will not work here. Paste the real key as Authorization: Bearer ak_…, or use a host-side stdio injector.

Grok Bot MCP config

{
  "mcpServers": {
    "steve-memo": {
      "url": "https://mcp.steve-memo.com/mcp",
      "headers": {
        "Authorization": "Bearer ak_…"
      }
    }
  }
}

Troubleshooting

  1. “Failed to load MCP server” is a generic client error. Check the MCP log or server response for the cause.
  2. A 401 missing_token response means the Authorization: Bearer header did not arrive.
  3. A common cause is pasting the literal ${env:STEVE_MEMO_CURSOR_API_KEY} or ${STEVE_MEMO_GROK_API_KEY} on a host that does not expand env vars. Grok Bot, Claude Desktop, and stdio need the real key. CLI and stdio read STEVE_MEMO_ORG_API_KEY.
  4. Some hosts cannot edit headers after adding a server. Remove it and add it again.
  5. A stdio injector is a host-side fallback, not a Steve Memo product.

Skill

Same file for every host. Save it to the path for that client.

Cursor
~/.cursor/skills/steve-memo/SKILL.md
Claude Code
~/.claude/skills/steve-memo/SKILL.md
Grok CLI
~/.grok/skills/steve-memo/SKILL.md

Open the raw skill