Wolfloyee

npx add-mcp 'https://wolfloyee.com/mcp'

Clients

What this connector can do

This page is the public connector for the Wolfloyee company dashboard. You create a key in Settings, paste https://wolfloyee.com/mcp, and call the same tools from Cursor, Claude, Codex, Grok, OpenClaw, Hermes, or Paperclip. There is no desktop package to install and no per-client secret besides the Bearer token you copy once.

Live tools cover Team Harmony pulse send and status, scores after n≥3, office seats on the company floor, people and work mode, and Slack bind status. That is the same surface a manager sees after login, minus the employee panel. If a client cannot send a custom Authorization header, it cannot talk to this MCP.

What stays out of scope

Employee-panel data, personal Address or Family fields, and survey answer rows are not in this connector. The MCP is a company-admin path, not a way to read who said what on a pulse. Insights still wait for three answers. A key does not bypass anonymity.

Do not paste a production key into a public gist or a shared Slack channel. Wolfloyee stores only a hash. If a key leaks, revoke it in Settings and create another. Public beta is free; after beta the company pays $1 per employee at month end for that month’s headcount.

URL, Bearer token, and Settings

The MCP URL is https://wolfloyee.com/mcp for every client. Cursor uses mcp.json or Settings → MCP. Claude Desktop and Claude Code take an HTTP server plus headers. Codex uses config.toml. Grok, OpenClaw, Hermes, and Paperclip use the same URL and Bearer pair. Paste the full Settings key, including wlk_, over the entire wlk_YOUR_KEY placeholder. Do not strip or double the prefix.

Sign in as the company first. Open Settings. Create an API key. Copy it immediately. Then add the URL from this page and Authorization: Bearer. After that, call a real dashboard action so you know the client is bound: pulse status, office seats, or Slack bind. Related pages: homepage, Company Settings after login, About, and What’s new.

MCP URL

https://wolfloyee.com/mcp

Authorization

Bearer wlk_YOUR_KEY

Paste the full Settings key, including wlk_. Replace the entire wlk_YOUR_KEY placeholder. Do not strip or double the prefix.

How to connect

1. 1 Create a key in Settings Sign in as the company. Open Settings. Create an API key. Copy the full key once, including wlk_. Wolfloyee stores only a hash.
2. 2 Add the same URL Use https://wolfloyee.com/mcp and Authorization: Bearer. Replace the entire wlk_YOUR_KEY placeholder with that full key. Cursor, Claude, Codex, Grok, OpenClaw, Hermes, and Paperclip all take that pair.
3. 3 Call a real dashboard action Tools are pulse (send, status, scores at n≥3), office seats, people, and Slack bind status. There is no employee-panel scope.

Client config

• Cursor Cursor Settings → MCP, or.cursor/mcp.json

  {
    "mcpServers": {
      "wolfloyee": {
        "url": "https://wolfloyee.com/mcp",
        "headers": {
          "Authorization": "Bearer wlk_YOUR_KEY"
        }
      }
    }
  }
  

• Claude Claude Desktop / Claude Code remote MCP

  {
    "mcpServers": {
      "wolfloyee": {
        "type": "http",
        "url": "https://wolfloyee.com/mcp",
        "headers": {
          "Authorization": "Bearer wlk_YOUR_KEY"
        }
      }
    }
  }
  

• Codex Codex config.toml

  [mcp_servers.wolfloyee]
  url = "https://wolfloyee.com/mcp"
  http_headers = { Authorization = "Bearer wlk_YOUR_KEY" }
  

• Grok Same URL + Bearer as the other HTTP clients

  {
    "mcpServers": {
      "wolfloyee": {
        "url": "https://wolfloyee.com/mcp",
        "headers": {
          "Authorization": "Bearer wlk_YOUR_KEY"
        }
      }
    }
  }
  

• OpenClaw OpenClaw MCP servers map

  {
    "mcpServers": {
      "wolfloyee": {
        "url": "https://wolfloyee.com/mcp",
        "headers": {
          "Authorization": "Bearer wlk_YOUR_KEY"
        }
      }
    }
  }
  

• Hermes Hermes MCP client HTTP server

  {
    "mcpServers": {
      "wolfloyee": {
        "url": "https://wolfloyee.com/mcp",
        "headers": {
          "Authorization": "Bearer wlk_YOUR_KEY"
        }
      }
    }
  }
  

• Paperclip Paperclip HTTP / MCP adapter

  {
    "mcpServers": {
      "wolfloyee": {
        "url": "https://wolfloyee.com/mcp",
        "headers": {
          "Authorization": "Bearer wlk_YOUR_KEY"
        }
      }
    }
  }
  

Public GitHub listing

The remote MCP listing is a public GitHub repository: README, MIT license, Cursor mcp.json, and Official MCP Registry server.json. It does not include the Wolfloyee application or API keys.

github.com/bonbrainllc/wolfloyee-mcp

If the client cannot see tools

A 401 usually means the Authorization header never left the client, or the key was truncated. Paste the full Settings key, including wlk_, over the entire wlk_YOUR_KEY placeholder. Do not wrap it in quotes inside the Bearer value. Revoke a leaked key in Settings and create another. Wolfloyee stores a hash, not the secret.

Empty scores are not a connector bug when fewer than three people have answered. Pulse send and status still work. Insights wait for n≥3, same as the dashboard. Office seats and people tools need a company plan and roster. Slack bind reports whether the workspace is claimed. There is no employee-panel scope on this URL.

Use https://wolfloyee.com/mcp for every client listed on this page. A localhost MCP package is the wrong path. After the config saves, call pulse status or Slack bind once so you know the Bearer token is live. Then go back to the dashboard if you need a human UI.