Skip to main content
Call tools/list on the server actually connected to this host. Remote OAuth and local stdio have separate catalogs; read the returned schema before supplying arguments.

Remote OAuth tools

The OpenAI and Claude plugins share these individually named tools. The full OpenAPI plus MCP coverage metadata is the Master Tool Contract. api_reference reads bounded summaries or one operation’s schema, its corresponding tools or explicit support limitation, and the compiled contract hash; it never executes an API request. A host may still be checking a new or changed tool, so this server catalog is not proof of current native visibility. Master Tool Contract SHA-256: 61ed92a391a6fc6c187cab53c0e0307dcc45652563857384745d0d8aab25dde0. These are the shared remote server’s named tools; discover the current host’s exact input schema with tools/list. New definitions may still be undergoing host checks.

Local stdio tools

The following catalog is generated from the shipped ohmyhost-mcp local client. It includes workflows that need a local filesystem or private credential input. Download complete local tool schemas · Complete API contract · Connect MCP · Task Skills. A listed tool does not grant account access. The API checks the current user, organization, project, environment and action. Use the existing project context before changes, and retain mutation idempotency keys across uncertain responses.

Source tools

Sources and versions explains the source choice, revision guards, save completion and restoration. Read source_get before choosing a source. Request include_binding: true for connection/generation guards; the default GitHub status view remains unchanged, while managed source is always complete. Preserve the selected project and source. For a complete native-chat snapshot, use remote source_upload_prepare and source_blob_put, then source_upload_commit for initialize/commit or source_switch for an explicitly requested GitHub-to-managed switch. source_blob_put computes hashes and byte lengths from real file contents; keep its exact receipts for every file, including unchanged retained files. The final manifest must match all receipts from this upload. Observe the original operation with source_upload; these tools neither read a local directory nor start deployment. Complete-tree flow. MCP text reads default to content_text with encoding: "utf8", with a base64 fallback for binary files. source_changes accepts exactly one content_text or content_base64 per path; content_base64: null deletes the file. REST uses base64. The editing example includes the complete argument shape. Both catalogs describe server support, not account authorization. Discover this native host’s actual remote tools through tools/list; local directory tools cannot operate inside a native chat without a local filesystem. Connection and publishing permissions are described in MCP setup.