Core Concepts
This page explains the words used across InstaMCP.
Bridge
A bridge connects InstaMCP to your API. You create a bridge from an OpenAPI or Swagger document. InstaMCP reads the API description and turns selected API operations into AI-callable tools.
Tool
A tool is one API action the AI agent can use, such as:
- Look up an order.
- Create a ticket.
- Search products.
- Update a booking.
You control which tools are enabled.
MCP
MCP means Model Context Protocol. In InstaMCP, an MCP deployment is the live runtime that lets the AI agent call the tools generated from your bridge.
Integration
An integration is the customer-facing AI agent experience you publish. It controls:
- Which bridge deployments are available.
- Which model is used.
- What instructions the AI agent follows.
- Which domains can load the widget.
- Which optional features are enabled.
Widget
The widget is the chat or voice interface installed in your website or app. Visitors use the widget; they do not need an InstaMCP account.
Double-Hop Authentication
Double-hop authentication lets your app pass the visitor's own auth context to InstaMCP so API calls can run as that visitor.
Use this when your API needs to answer questions like:
- "Show my orders."
- "Cancel my booking."
- "Update my profile."
See Double-Hop Authentication.
Host Capabilities
Host capabilities let your app tell the widget which website or app actions are available, such as opening a page, selecting an item, or starting a checkout flow.
See Host Capabilities.
Canvas
Canvas lets the AI agent render structured views in the widget, such as product grids, comparison tables, KPI cards, or markdown panels.
See Canvas.
Correction Memory
Correction Memory lets your AI agent learn from approved corrections so it is less likely to repeat the same mistake in future conversations.
It is model-agnostic, so accepted corrections can remain useful even if you later switch the integration to another model.
See Correction Memory.