Captia Technology

Captia Technology

Captia MCP Server

Connect your AI agent to Captia industrial knowledge: protocol glossary, technical resources and OEE calculation. Public, read-only and no authentication required.

What it is

The Model Context Protocol is the standard interface an AI assistant uses to query external data and tools. This server exposes Captia published knowledge so an agent can query it directly instead of reading pages.

Endpoint

https://www.captiatechnology.com/api/mcp/

The trailing slash is required. Without it the endpoint responds with a redirect and the client may lose the request.

Configuration

In Claude Desktop and compatible clients, add this block to your MCP servers configuration:

{
  "mcpServers": {
    "captia": {
      "type": "http",
      "url": "https://www.captiatechnology.com/api/mcp/"
    }
  }
}

Tools

get_company_profile

Captia Technology identity: legal entity, offices, contact and the five business units.

Parameters

  • localeResponse language: es or en. Defaults to es.

get_glossary_term

Definition of an industrial term from the glossary: protocols, OT/IT concepts, industrial AI and energy. If there is no confident match it returns suggestions instead of a wrong definition.

Parameters

  • termrequiredTerm to look up, by slug or visible label. Example: opc-ua, OEE.
  • localeResponse language: es or en. Defaults to es.

search_knowledge

Search across published technical resources: guides, comparisons and articles on industrial data, OT/IT integration, industrial AI and energy.

Parameters

  • queryrequiredSearch terms.
  • limitMax results, 1 to 20. Defaults to 5.
  • localeResponse language: es or en. Defaults to es.

list_protocols

The industrial protocols Captia Connect ingests data from, with family and summary.

Parameters

  • localeResponse language: es or en. Defaults to es.

compare_protocols

Compare two or more industrial protocols by family, summary, how Connect ingests them and target keywords. It does not expose throughput or transport specs: they are not published as structured data.

Parameters

  • slugsrequired2 to 6 protocol slugs. Use list_protocols to get valid values.
  • localeResponse language: es or en. Defaults to es.

calculate_oee

Computes availability, performance, quality and OEE from shift data. Same formula as the published calculator, so results always match the website.

Parameters

  • plannedMinutesrequiredPlanned production time, in minutes.
  • downtimeMinutesrequiredUnplanned downtime plus changeovers, in minutes.
  • idealCycleSecondsrequiredIdeal cycle time, in seconds per piece.
  • totalPiecesrequiredTotal pieces produced.
  • defectPiecesrequiredDefective pieces: rejects plus rework.
  • localeResponse language: es or en. Defaults to es.

What it does not do

  • No access to plant or customer data. It only serves knowledge already published on this site.
  • It never writes or changes anything: every tool is read-only.
  • Protocol comparison does not expose throughput or transport specs, because they are not published as structured data.