Skip to main content
An integration is all of one website’s tools, published as its own MCP server and REST API, so an agent that only needs Google Flights can connect to Google Flights alone.

​
Choose how to connect

Every tool belongs to its website’s integration, and each new build for that site adds to it. The same tools also run through the Pomerado MCP.

​
What an integration MCP lists

  • One tool per site tool, under its own name, such as search_flights. Each takes its input as a plain object and needs no tool_id.
  • build_tool, which adds a tool for this website. See Build a tool.
  • manage_login, which gives the person a link to save or replace their login for the site.
  • get_job, answer_job and cancel_job, to follow runs and builds. See Wait for a result.
Read tools are marked read-only, so clients may run them in parallel. The full layout is in the integration MCP reference.

​
Use its REST API

  • POST /v1/integrations/{id}/tools/{tool_id}/runs runs one of its tools.
  • GET /v1/integrations/{id}/openapi.json answers an OpenAPI document with one operation per tool.
  • GET /v1/integrations/{id}/reference answers a Markdown reference with setup for each client and a sample call for each tool.

​
Find integrations

GET /v1/integrations lists the public catalog; add mine=true for integrations holding tools you built. Through the Pomerado MCP, call call_pomerado_api with integrations.list. Each integration also has a page on the Dashboard.

​
Next steps