AI AGENTS

Give your agents eyes

One source of truth your team and their AI agents can query.

The Problem

An agent doing deploy or incident work has two bad options for context: trust documentation that was true when it was written, or hold read credentials for every platform it might need to check. The first gives confident answers from stale facts. The second is a permission set no security team wants to grant, spread across cloud accounts, hypervisors, and clusters, each with its own auth model.

The Solution

Give the agent write access to the one system it operates, and read access to Parascope for everything else. One query surface covers what exists, how it connects, what changed, and what it looked like before. Answers carry freshness information, so the agent can judge how current its context is.

The questions agents ask

Read-only MCP tools cover discovery, change history, relationships, impact, and querying. These are the ones agents reach for first.

What changed on this host in the last four hours?

get_changes

Every configuration change with before-and-after state, across every source that observed the host, in one feed.

What breaks if this node goes down?

get_impact

Walks the dependency graph outward from the failure point and returns affected systems ranked by criticality and distance.

What depends on this database?

get_relationships / get_lineage

Incoming and outgoing dependency edges, and the full stack lineage from application tier down to physical hardware.

What did this look like before the incident?

get_ci_at

Point-in-time configuration state for any CI, covering the past year. The question source systems cannot answer.

Anything else?

execute_paraql / natural_language_query

Full ParaQL for arbitrary questions, or plain English translated to ParaQL. Staleness functions let the agent check how fresh its answer is.

MCP server

Per tenant at https://{your-tenant}.parascope.io/mcp, with OAuth through your tenant's SSO. Works with any MCP-compatible agent. The tool surface is read-only: context, never control. Read the setup guide.

REST API + ParaQL

A single read-only API key covers search, change history, relationships, impact, and ParaQL over HTTP. Temporal queries (AS OF) cover the past 365 days, and staleness functions report how fresh each answer is.

A paraql command-line client (interactive REPL, JSON output for scripts and agents) is in progress. See the roadmap.

Two ways to give an agent context

Wire it into every platform

  • Credentials for each cloud, cluster, and hypervisor
  • Scopes that usually include write access
  • A different output format per system
  • Current state only; no history
  • No cross-system relationships

Point it at Parascope

  • One read-only credential
  • No write path, by design
  • One query language across every source
  • Full change history and point-in-time state
  • Relationships and blast radius built in

More on the trust model on the security page, and on querying on the ParaQL page. Background reading: Infrastructure-Aware Agents.

See Parascope in action

Explore a live environment. No signup required.

Try the demoStart free trial