Connect an MCP client

Option A — OAuth (recommended)

For clients that support remote MCP servers with OAuth, just enter the URL above. The client discovers our authorization server automatically, opens a browser for you to sign in, and shows a consent screen where you pick what the agent may access. No tokens to copy. Access tokens are short-lived and refresh automatically, and you can disconnect any app anytime from MCP settings.

We start you with read-only scopes — grant write or admin access only if you intend the agent to change your data.

Option B — Personal access token (dev / power users)

Create a scoped token at MCP settings and send it as a Bearer header. Best for local development and CLI agents. The token is shown once — store it like a password.

Clients that accept a remote URL + headers:

{
  "mcpServers": {
    "hardlysimple": {
      "url": "https://hardlysimple.com/mcp",
      "headers": {
        "Authorization": "Bearer ${HARDLYSIMPLE_PAT}"
      }
    }
  }
}

Clients that only run a local (stdio) bridge — use mcp-remote:

{
  "mcpServers": {
    "hardlysimple": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://hardlysimple.com/mcp"
      ]
    }
  }
}

With mcp-remote you can pass the token via --header Authorization:"Bearer $HARDLYSIMPLE_PAT", or let it run the OAuth flow in your browser (omit the header). Never paste a token into a client you don't trust.

Per-client notes

• ChatGPT — enable Developer Mode / custom connectors, add the MCP server URL above, and complete the OAuth consent. Start with read-only scopes.
• Claude / Cursor — if the client supports remote MCP servers, add the URL and authorize over OAuth. If it only supports local/stdio config, use the mcp-remote bridge above.
• Codex / CLI agents — use the PAT Bearer header, or the mcp-remote bridge.

Scopes

Scopes restrict what a connection can do; they never grant more than your own account already has.

• Read your workspace — View your teams, tasks, sketches, decks (presentations and decision decks), knowledge bundles, databanks, design systems, structured data, repositories, Claude artifacts, and agent workflows.
  hardlysimple:teams:readhardlysimple:tasks:readhardlysimple:sketches:readhardlysimple:knowledge-bundles:readhardlysimple:databanks:readhardlysimple:design-systems:readhardlysimple:structured-data:readhardlysimple:repositories:readhardlysimple:claude-artifacts:readhardlysimple:presentations:readhardlysimple:halfabs:readhardlysimple:decks:readhardlysimple:workflows:read
• Edit your workspace — Create and update your tasks, sketches, decks (presentations and decision decks), knowledge bundles, databanks, team design systems, structured data, repositories, filed Claude artifacts, and agent workflow drafts.
  hardlysimple:tasks:writehardlysimple:sketches:writehardlysimple:knowledge-bundles:writehardlysimple:databanks:writehardlysimple:design-systems:writehardlysimple:structured-data:writehardlysimple:repositories:writehardlysimple:claude-artifacts:writehardlysimple:presentations:writehardlysimple:halfabs:writehardlysimple:decks:writehardlysimple:workflows:write
• Upload files — Upload images and files into your databanks and onto task cards.
  hardlysimple:databanks:uploadhardlysimple:tasks:upload
• Read your profile — View your name, email, and profile details.
  hardlysimple:profile:read
• Manage task assignments — See what's assigned to you and assign people to tasks.
  hardlysimple:tasks:assign:readhardlysimple:tasks:assign:write
• Companion sessions — Identify itself (provider, model, effort) and track its work as a session.
  hardlysimple:companions:readhardlysimple:companions:write
• Your calendar — See your unified calendar — including linked Google accounts — and add or remove events on your own calendars.
  hardlysimple:calendar:readhardlysimple:calendar:write
• Administer your workspace — Full administrative access (only effective if your account is an admin).
  hardlysimple:admin