Skip to main content
Every Conduit MCP tool falls into one of three classes. Use them to decide which tools a client may run without asking. The readOnlyHint annotation on each tool matches its class: true for Read, false for both write classes. A tool that both reads and writes is classified as a write.

Connection permissions

The OAuth consent screen always lets you choose Read only or Read and write, whatever access the client requested, and the connection gets the level you choose. ChatGPT requests read-only access, so ChatGPT users should choose Read and write to use write tools. A read-only connection can call Read tools only; every write tool returns an error result (isError: true) with code forbidden. API tokens follow the same rule: a read-only capi_ token rejects every write tool.

Search mode

OAuth and API-token connections list two tools, search_tools and call_tool, and reach every tool below through them. The Conduit ChatGPT plugin is the exception: it lists every tool below individually, so approve each tool by its own class.

Sensitive write

These tools act on people or property outside Conduit, or cannot be undone. send_conversation_message and send_ticket_message accept an idempotency_key, but most channels do not yet use it to block a duplicate. Do not retry a send that may have succeeded.

Write

Read

Knowledge, booking, and web tools

These tools come from Conduit’s knowledge service and appear in search_tools alongside the tools above.