Integration

Range integration

Range is a team check-in and team directory tool (async standups, goals, meetings). Read the organization's teams with their members, followers, parent and child teams; look up users by id, by email or by a linked identity on another service; read the user who owns the key; and pull check-ins (updates) by a user, a team or the whole organization within a time window, with their line items (snippets) and integration attachments. This integration is read-only: creating teams, joining or leaving teams, editing user profiles or state and recording integration activity are not exposed. Authentication is a Range API key from the developer settings, sent with HTTP Basic auth as the username with an empty password; the key acts with the privileges of the user who created it.

Connect Range How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Range.Built from the 8 Range tools below, on the connection you add once.

What you can do with Range

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

User, 4 operations

find_userFind userGETLooks up a Range user by email, email hash or a linked identity on another service. Returns the user id, plus the full user when include_refs is true.
get_auth_userGet auth userGETReturns the user who owns the API key, and that user's organization.
get_userGet userGETLooks up one user by their Range user id and returns the full user: profile, and the state when the key's user is that user or an admin.
list_usersList usersGETLists the users of an organization, optionally narrowed to one team, to an explicit set of user ids, or to the teammates of a user.

Team, 3 operations

get_teamGet teamGETFetches one team with its directly related users, its ancestors (ordered from the root of the organization) and all its descendant teams.
list_teamsList teamsGETLists the teams associated with the organization of the API key, together with the users and the parent and child teams they reference.
list_user_teamsList user teamsGETLists the teams associated with one user, together with the users and the parent and child teams they reference.

Check in, 1 operation

list_updatesList updatesGETLists check-ins (updates) by a user, a team, the organization or a user's teammates, optionally in a time window. include_refs adds the snippets, attachments and users referenced.

Use Range from Claude Code, Cursor or Codex

Connect Range in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Range operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Range

Create your workspace
Sign up free. Nothing to install.
Connect Range once
Add your Range connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.