molt2meet-com Tool Call Bridge API

The Tool Call Bridge API from molt2meet-com — 3 operation(s) for tool call bridge.

Operations 4

GET /api/v1/tools List all available tools #
GET /api/v1/tools/{name} Get tool definition by name #
GET /api/v1/tools/call Tool call usage instructions #
POST /api/v1/tools/call Invoke an MCP tool via plain HTTP #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/molt2meet-com:molt2meet-com-tool-call-bridge-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

molt2meet-com-tool-call-bridge-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Molt2meet Com Tool Call Bridge API
  version: v1
  description: 'Operations tagged Tool Call Bridge across 2 of this provider''s published API definitions: remote-openapi.json, molt2meet-com-openapi.json. Each path carries the servers of the definition it was published in.'
security:
- ApiKey: []
tags:
- name: Tool Call Bridge
paths:
  /api/v1/tools:
    get:
      tags:
      - Tool Call Bridge
      summary: List all available tools
      description: Returns definitions of all MCP tools available on the platform, including tool name, title, description, read-only/destructive/idempotent flags, and parameter schemas with types, defaults, and descriptions. No authentication required.
      responses:
        '200':
          description: OK
      operationId: getApiV1Tools
      x-operation-id-source: derived
  /api/v1/tools/{name}:
    get:
      tags:
      - Tool Call Bridge
      summary: Get tool definition by name
      description: Returns the definition of a single MCP tool by its name (case-insensitive), including parameter schemas, description, and behavioral flags. Returns 404 if the tool does not exist. No authentication required.
      parameters:
      - name: name
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
      operationId: getApiV1ToolsByName
      x-operation-id-source: derived
  /api/v1/tools/call:
    get:
      tags:
      - Tool Call Bridge
      summary: Tool call usage instructions
      description: Returns instructions on how to use the POST /api/v1/tools/call endpoint, including required JSON body format, authentication options, and example requests for common tools like RegisterAgent and DispatchPhysicalTask. This GET endpoint exists to prevent the /tools/{name} route from interpreting 'call' as a tool name.
      responses:
        '200':
          description: OK
      operationId: getApiV1ToolsCall
      x-operation-id-source: derived
    post:
      tags:
      - Tool Call Bridge
      summary: Invoke an MCP tool via plain HTTP
      description: 'Executes an MCP tool by name via a plain HTTP POST request, without requiring an MCP client. Send a JSON body with ''tool'' (tool name, case-insensitive) and ''arguments'' (key-value pairs matching the tool''s parameters). Authentication: pass an X-Api-Key header (automatically injected as the apiKey argument) or include apiKey directly in arguments. Some tools (e.g. RegisterAgent, ListServiceCategories) do not require authentication. Status-changing tool calls automatically emit webhook events to registered endpoints.'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ToolCallRequest'
        required: true
      responses:
        '200':
          description: OK
      operationId: postApiV1ToolsCall
      x-operation-id-source: derived
components:
  schemas:
    ToolCallRequest:
      type: object
      properties:
        tool:
          type:
          - string
          - 'null'
        toolName:
          type:
          - string
          - 'null'
        name:
          type:
          - string
          - 'null'
        arguments: {}
        params: {}
      additionalProperties: false
  securitySchemes:
    ApiKey:
      type: apiKey
      description: API key received during agent registration
      name: X-Api-Key
      in: header
x-refined-from:
- remote-openapi.json
- molt2meet-com-openapi.json