Integration

LargerIO integration

LargerIO detects the web technologies a website uses (CMS, frameworks, analytics, ecommerce, hosting and more) across about 22 million crawled domains and 5,700 technologies. Look up a domain's technology stack, list the technologies of a category, read one technology's adoption details and top sites, and list trending technologies. Calls spend the account's monthly token balance: catalog reads are free, technology details 1 token, a cached lookup 1, a quick lookup 5 and a full lookup 100; a free verified account gets 2,000 tokens a month (reset on the 1st, UTC), and the API allows 60 requests and 10 lookups a minute. E-mail addresses found on scanned sites are not returned; data exports, the category index and the name search are not exposed (the vendor documents no response shape for those two lists). Authentication is a personal access token created under API keys on larger.io (free account with a verified e-mail), sent as a Bearer token.

Connect LargerIO How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with LargerIO

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.

Category, 1 operation

list_category_technologiesList category technologiesGETLists the technologies in one category, by category slug (for example cms, analytics or ecommerce). Free: costs no tokens. Answers 404 for an unknown category.

Domain, 1 operation

lookup_domainLookup domainGETDetects the technologies a website uses. Spends tokens: quick 5, full 100 (at most 1 full a minute), or 1 when a result under 6 hours old is reused (cached true). Answers 502 when the scan fails, 504 on timeout.

Technology, 1 operation

get_technologyGet technologyGETReturns one technology's details: adoption, top domains using it and language distribution. Costs 1 token. Answers 404 for an unknown technology slug.

Trending, 1 operation

list_trending_technologiesList trending technologiesGETLists the technologies LargerIO currently reports as trending. Free: costs no tokens. Use a technology slug from the answer with get_technology.

Use LargerIO from Claude Code, Cursor or Codex

Connect LargerIO in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its LargerIO 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 LargerIO

Create your workspace
Sign up free. Nothing to install.
Connect LargerIO once
Add your LargerIO 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.