Skip to directory

Dialpad via Composio

Composio (third-party mediated Dialpad toolkit; not vendor-operated)

Streamable HTTP7+ documented tools0

About Dialpad via Composio

Access selected Dialpad operations through Composio Connect's shared MCP server and dynamically discovered toolkit actions.

What you can use it for

  • Manage Dialpad calls, users, offices, channels, contacts, numbers, SMS, callbacks and webhooks through Composio.
Connection and setup
Hosting
Composio-hosted remote MCP; upstream provider API accessed through a third-party toolkit
Transport
Streamable HTTP
Endpoint
https://connect.composio.dev/mcp
Authentication
OAuth 2.0 or API key; Composio-managed OAuth is documented. Composio Connect prompts the user to authorize or configure the provider connection; Composio-managed OAuth availability depends on the toolkit.

Requirements

  • A Dialpad account with permissions for the requested data and actions.
  • A Composio account and MCP client supporting Streamable HTTP.
  • Provider authorization or credentials as specified on the linked toolkit page.

Setup steps

  1. Add https://connect.composio.dev/mcp as a remote Streamable HTTP MCP server.
  2. When needed, ask the client to connect the Dialpad app; complete the provider authorization in the browser or the secure credential flow.
  3. Use Composio tool search to discover available actions and fetch their schemas; the shared MCP exposes meta-tools rather than a fixed per-provider tools/list.
  4. Start with a read-only query. Confirm before creating, sending, changing, or deleting provider data.
Tools 7+

Current Composio toolkit reference reports 192 provider actions and exposes their identifiers in its toolkit catalog. Connect dynamically discovers account-available actions; no live account tools/list is represented here.

  • COMPOSIO_SEARCH_TOOLS

    Search the Composio action catalog for tools relevant to a request and return a suggested execution plan.

    01
  • COMPOSIO_GET_TOOL_SCHEMAS

    Fetch input schemas for tool slugs returned by search.

    02
  • COMPOSIO_MULTI_EXECUTE_TOOL

    Execute one or more discovered provider tools in parallel across connected apps.

    03
  • COMPOSIO_MANAGE_CONNECTIONS

    Create, list, rename, or remove OAuth connections to upstream apps.

    04
  • COMPOSIO_WAIT_FOR_CONNECTIONS

    Wait for a user to complete an OAuth connection flow.

    05
  • COMPOSIO_REMOTE_WORKBENCH

    Run Python in a remote sandbox for bulk operations and processing large tool responses.

    06
  • COMPOSIO_REMOTE_BASH_TOOL

    Run Bash in a remote sandbox for file processing and large data handling.

    07

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Third-party platform-mediated integration, not a standalone or vendor-hosted MCP server.
  • Available actions depend on Composio toolkit version, provider permissions, account plan, and authorization.
  • Account plan and user permissions determine which operations are available.
  • The toolkit contains communication and admin mutations; confirm before sending or changing settings.
  • Connection and functionality were not tested in this research pass.
Original sources
  • third party mcp setup

    Composio documents the shared endpoint, Streamable HTTP transport, dynamic app authorization, and seven shared meta-tools.

  • third party toolkit reference

    Composio’s current Dialpad toolkit reference reports 192 provider tools/actions and publishes named action identifiers. Connect uses shared MCP meta-tools and dynamic provider action discovery; the count is toolkit-wide, not the live tools/list for one account.

  • official crawl4ai verification

    Crawl4AI 0.9.5 fetched Composio Connect docs and verified seven shared meta-tool identifiers. Provider toolkit actions are selected dynamically.

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.