Integration

Botify integration

Botify is an enterprise SEO platform that crawls websites and joins the crawl with log files, Google Search Console and analytics data. List the projects of a Botify account and their crawl analyses, read an analysis summary, crawl statistics, sitemap, inlink, PageRank and segment reports, inspect the crawl data of one URL, run BQL queries, launch, pause or resume a crawl, and start and follow export jobs. The legacy Google Analytics orphan URL report, the duplicate unpaginated project listing and the BQLv1 aggregation routes (whose documented answer omits the aggregated values) are not included. Authentication is the API token from the Tokens panel of your Botify account page, sent in the Authorization header after the word Token.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Botify

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Export, 3 operations

  • create_urls_exportCreate urls exportPOSTAgents: ask firstStarts a CSV export of the URLs of one analysis matching a BQLv1 query (fields, filters, sort). Returns the export job; follow it with get_urls_export until job_status is DONE or FAILED.
  • get_urls_exportGet urls exportGETAgents: ask firstReturns the status of one URL export job of an analysis: job_status, the number of exported URLs and, once the job has finished, its results.
  • list_urls_exportsList urls exportsGETAgents: ask firstLists the URL export jobs of an analysis with their status, number of results and query.

Job, 3 operations

  • create_jobCreate jobPOSTAgents: ask firstCreates a job, typically an export of a BQL query: job_type export with a payload giving username, project, export_size, formatter, connector and query. Follow it with get_job.
  • get_jobGet jobGETAgents: ask firstReturns one job: its type, status (CREATED, PENDING, PROCESSING, DONE or FAILED), payload and, once finished, its results.
  • list_jobsList jobsGETAgents: ask firstLists the jobs of the account (exports and other job types), with their status, payload and results. Filter by job_type, project or analysis.

Url, 3 operations

  • get_url_detailGet url detailGETAgents: ask firstReturns the crawl data Botify stored for one URL of an analysis. Pass fields to choose which datamodel fields come back.
  • list_latest_crawled_urlsList latest crawled urlsGETAgents: ask firstReturn a list of 1000 latest URLs crawled (all crawled URLs or only URLS with HTTP errors)
  • query_analysis_urlsQuery analysis urlsPOSTAgents: ask firstRuns a BQLv1 query on the URLs of one analysis (fields to return, filters, sort) and returns one page of matching URLs. query_project with BQLv2 is the newer way to query several collections.

Analyse, 2 operations

  • get_analysisGet analysisGETAgents: ask firstReturns the detail of one crawl analysis: its owner, slug, status, features, configuration, URL counts and launch and finish dates.
  • list_analysesList analysesGETAgents: ask firstLists the crawl analyses of a project with their slug, status, launch and finish dates and URL counts. Set only_success=false to include analyses that did not finish successfully.

Collection, 2 operations

  • get_collectionGet collectionGETAgents: ask firstGet the detail of a collection
  • list_collectionsList collectionsGETAgents: ask firstList all collections for a project

Filter, 2 operations

  • get_saved_filterGet saved filterGETAgents: ask firstRetrieve a specific project saved, account or recommended filter's name, ID and filter value
  • list_saved_filtersList saved filtersGETAgents: ask firstList all the project's saved filters (each filter's name, ID and filter value)

Robots txt indexe, 2 operations

  • get_robots_txt_fileGet robots txt fileGETAgents: ask firstReturns the content of one robots.txt file found during an analysis, by the file name listed by list_robots_txt_files.
  • list_robots_txt_filesList robots txt filesGETAgents: ask firstReturn an object containing all robots.txt files found on the project's domains. The object is null for virtual robots.txt.

Account filter, 1 operation

  • list_account_filtersList account filtersGETAgents: ask firstList all the account saved filters

Ai, 1 operation

  • get_url_ai_suggestionsGet url ai suggestionsGETAgents: ask firstGets AI suggestions of an URL for an analysis

Clone, 1 operation

  • clone_keyword_groupsClone keyword groupsPOSTAgents: ask firstCopies every keyword group of this project to another project of the target user.

Crawl statistic, 1 operation

  • get_crawl_statisticsGet crawl statisticsGETAgents: ask firstReturn global statistics for an analysis

Datamodel, 1 operation

  • get_urls_datamodelGet urls datamodelGETAgents: ask firstReturns the datamodel of an analysis: every field that query_analysis_urls and create_urls_export can return or filter on, with its id, type and group.

Dataset, 1 operation

  • get_urls_datasetsGet urls datasetsGETAgents: ask firstReturns the datasets of an analysis: the groups of fields available for URL queries, with each field's id, type and suggested operations.

Datasources summary by project, 1 operation

  • get_datasources_summaryGet datasources summaryGETAgents: ask firstReturns, for every project of a user, its data sources with the date of their last successful revision and the status of their last revision.

Domain, 1 operation

  • list_top_linked_domainsList top linked domainsGETAgents: ask firstLists the top external domains linked from the crawled pages, with follow and nofollow link counts and sample links for each domain.

Html, 1 operation

  • get_url_htmlGet url htmlGETAgents: ask firstReturns the HTML Botify stored for one URL of an analysis. Available when the analysis kept raw pages (has_raw_pages in get_analysis).

Launch, 1 operation

  • launch_analysisLaunch analysisPOSTAgents: ask firstCreates and launches a new crawl analysis for a project.

Light, 1 operation

  • list_analyses_lightList analyses lightGETAgents: ask firstLists the crawl analyses of a project with a lighter record per analysis (slug, name, status, dates, URL counts) than list_analyses.

Lost, 1 operation

  • get_lost_pagerankGet lost pagerankGETAgents: ask firstReturns how much internal PageRank an analysis loses to non-crawled URLs, to external links and to URLs blocked by robots.txt.

Orphan url, 1 operation

  • list_visits_orphan_urlsList visits orphan urlsGETAgents: ask firstList of Orphan URLs. URLs which generated visits from the selected source according to Google Analytics data.

Out of config, 1 operation

  • list_sitemap_urls_out_of_configList sitemap urls out of configGETAgents: ask firstSample list of URLs which were found in your sitemaps but outside of the crawl perimeter defined for the project.

Pause, 1 operation

  • pause_analysisPause analysisPOSTAgents: ask firstPauses a running crawl analysis. Resume it with resume_analysis.

Percentile, 1 operation

  • get_inlinks_percentilesGet inlinks percentilesGETAgents: ask firstReturns the inlinks percentiles of an analysis: for each percentile bucket of crawled URLs, the minimum, maximum and average number of inlinks.

Project, 1 operation

  • list_projectsList projectsGETAgents: ask firstLists the active projects of a Botify user or organization, with their slug, name and settings. Filter by project name.

Query, 1 operation

  • query_projectQuery projectPOSTAgents: ask firstRuns a BQL (BQLv2) query on a project: collections and periods to read, dimensions, metrics, filters and sort. Returns up to 2000 rows per page.

Report, 1 operation

  • get_sitemaps_reportGet sitemaps reportGETAgents: ask firstGet global information of the sitemaps found (sitemaps indexes, invalid sitemaps urls, etc.)

Resume, 1 operation

  • resume_analysisResume analysisPOSTAgents: ask firstResumes a paused crawl analysis.

Saved explorer, 1 operation

  • list_saved_explorersList saved explorersGETAgents: ask firstList all the project's Saved Explorers.

Segment, 1 operation

  • list_segmentsList segmentsGETAgents: ask firstGet the segments feature public metadata of an analysis.

Sitemap only, 1 operation

  • list_sitemap_only_urlsList sitemap only urlsGETAgents: ask firstSample list of URLs which were found in your sitemaps, within the project allowed scope (allowed domains/subdomains/protocols), but not found by the Botify crawler.

Stat, 1 operation

  • get_search_console_statsGet search console statsGETAgents: ask firstList clicks and impressions per day

Subdomain, 1 operation

  • list_top_linked_subdomainsList top linked subdomainsGETAgents: ask firstLists the top external subdomains linked from the crawled pages, with follow and nofollow link counts and sample links for each subdomain.

Summary, 1 operation

  • get_scoring_summaryGet scoring summaryGETAgents: ask firstReturns the scoring summary of an analysis, as computed by Botify for the crawl.

Time, 1 operation

  • get_crawl_statistics_over_timeGet crawl statistics over timeGETAgents: ask firstReturn crawl statistics grouped by time frequency (1 min, 5 mins or 60 min) for an analysis

Use Botify from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Botify once

    Add your Botify connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Botify integration FAQ

What can you do with the Botify integration?

LiveContext exposes 44 operations on Botify, covering export, job, url and analyse.

Popular integrations

Browse the whole catalog