Connected apps
Read the Apps catalog, connection states, and access rules for Hoko integrations.
Connection direction
ChatGPT is an inbound host. ChatGPT receives an Hoko OAuth grant and calls Hoko tools through MCP. Hoko does not call ChatGPT and does not receive a ChatGPT API key.
An OpenAPI document describes the Hoko API contract. It does not connect an external provider account.
Hoko does not list Slack, Notion, or another outbound provider as connected until that provider has a reviewed adapter, an authorization flow, and credential storage.
Host setup cards
The catalog contains setup guidance for these hosts:
These cards describe documented setup paths. They do not claim a native listing, one-click install, or Hoko verification. Use https://mcp.hoko.to as the canonical MCP endpoint. A manual MCP client that supports bearer headers can use this configuration after you create an API key in Dashboard → Integrations → API Keys:
{
"mcpServers": {
"hoko": {
"url": "https://mcp.hoko.to",
"headers": { "Authorization": "Bearer <HOKO_API_KEY>" }
}
}
}Keep the key in the host secret store. Use the host guide for the bounded private setup. Native account approval, public listing, and one-click distribution remain separate provider gates. Zapier, n8n, Make, and similar tools can call MCP or the REST API. Slack, Notion, and Linear can be automated through those tools and Hoko API calls; Hoko has no native outbound connectors for them.
API-key and bearer access covers the operations allowed by that key's scopes. It does not provide human-only profile, personal Apps, API-key management, upload, or billing access. Use the Dashboard for those features.
Outbound provider directory
The catalog contains 47 entries: 13 clients and 34 business systems. The Help app guides explain user setup. This reference records provider fields, supported contracts, and deployment requirements.
Availability distinguishes manual recipes from configured provider connections and public distribution. A documented recipe does not imply a native account connection or marketplace listing. Provider approval and app registration remain separate requirements.
A Hoko API key authenticates calls to Hoko. Provider credentials authenticate calls to the provider and remain in the customer-owned recipe or encrypted provider connection. They are not Hoko API keys. Use only the documented provider permissions; native OAuth, public registration, and incoming provider webhooks have their own requirements.
Use the automation recipes guide, the link.created receiver guide, and the Google Tag Manager template guide for the first customer-owned implementation paths.
Download the private Power Automate connector. Pipedream Workflows is archived because the provider is retiring Workflows and String. Hoko has not implemented a Pipedream Connect adapter.
The private Zapier actions add create-link and exact external-ID lookup setup. The local preview has no verified Zapier import or public listing. Every guide also has a README.md route for agents, listed in llms.txt.
The private n8n node adds Create Link and exact external-ID lookup actions. The package targets n8n 2.42.x with Node.js 24. This is a private, self-hosted package; n8n Cloud and community publication are not included.
The catalog distinguishes manual recipes from native provider connections and public distribution. Use the documented account permissions and current availability. A private recipe does not imply a native connection or marketplace listing.
Setup guides
This section keeps host-specific transport and credential reference. Follow each Help guide for the connection steps. OAuth hosts use their registered client settings; API-key clients use a scoped key from Dashboard → Integrations → API Keys.
ChatGPT
ChatGPT acts as an OAuth client of Hoko's authorization server. Its MCP resource is https://mcp.hoko.to. The host supplies client registration, the callback, and PKCE parameters. Hoko validates the resource, workspace grant, operation scopes, token refresh, and revocation.
Private connectors require an eligible ChatGPT account and a registered Hoko deployment. Registration and client authentication depend on that deployment; a public marketplace listing is a separate distribution step. Follow the Help guide for the browser connection flow.
Claude
Claude web and Claude Desktop use the Hoko MCP resource and OAuth authorization server. Claude owns its client registration, callback, and PKCE parameters; Hoko binds approved scopes to the selected workspace. Client authentication follows the configured deployment. Private connector availability depends on the Claude account; public distribution is separate. Follow the Help guide for account linking.
See Anthropic custom connectors for the host fields.
Claude Code
Add a remote HTTP MCP server with the CLI. Claude Code sends the header to Hoko for each request.
claude mcp add --transport http hoko https://mcp.hoko.to \
--header "Authorization: Bearer <HOKO_API_KEY>"See Claude Code MCP setup for the command and OAuth behavior.
Cursor
Add this entry to the project .cursor/mcp.json file. Use the host's secret interpolation for the key.
{
"mcpServers": {
"hoko": {
"url": "https://mcp.hoko.to",
"headers": { "Authorization": "Bearer ${env:HOKO_API_KEY}" }
}
}
}See Cursor MCP setup for the current configuration format.
VS Code
Add an HTTP server and a password input to .vscode/mcp.json or the workspace MCP settings.
{
"servers": {
"hoko": {
"type": "http",
"url": "https://mcp.hoko.to",
"headers": { "Authorization": "Bearer ${input:hoko-api-key}" }
}
},
"inputs": [
{
"type": "promptString",
"id": "hoko-api-key",
"description": "Hoko API key",
"password": true
}
]
}See VS Code MCP configuration for HTTP, OAuth, and secret input fields.
GitHub Copilot
Add Hoko as a remote HTTP MCP server in Copilot Chat or Copilot CLI. In Copilot CLI, the equivalent command is:
copilot mcp add --transport http \
--header "Authorization: Bearer <HOKO_API_KEY>" \
hoko https://mcp.hoko.toOrganization policy can disable remote MCP. Follow the host's current setup screen when the command is unavailable.
See GitHub Copilot CLI MCP setup for the command and header order.
Gemini CLI
Gemini CLI remains a supported Hoko MCP host for Gemini Code Assist Standard or Enterprise users and paid Gemini or Gemini Enterprise Agent Platform API keys. Consumer/free, Google AI Pro, and Google AI Ultra Gemini CLI access stopped serving requests on 2026-06-18. Google directs those users to Antigravity CLI.
Antigravity CLI is a separate client. Hoko has not verified its MCP transport, authentication, or feature parity, so this guide does not claim Antigravity support.
Add an HTTP server to Gemini CLI settings. Replace the placeholder with your Hoko API key in your local settings file. Gemini documents environment expansion for server env values, not for HTTP header values. Keep the settings file private and do not commit it.
{
"mcpServers": {
"hoko": {
"httpUrl": "https://mcp.hoko.to",
"headers": { "Authorization": "Bearer <HOKO_API_KEY>" }
}
}
}See Gemini CLI MCP setup for the httpUrl and header fields.
Windsurf
Add this server to Windsurf's MCP configuration. Windsurf uses serverUrl for a remote server.
{
"mcpServers": {
"hoko": {
"serverUrl": "https://mcp.hoko.to",
"headers": { "Authorization": "Bearer ${env:HOKO_API_KEY}" }
}
}
}See Windsurf Cascade MCP configuration for the host fields and supported remote transports.
Zapier
Open the Zapier MCP Client connection form. Choose a remote Streamable HTTP server, enter https://mcp.hoko.to, choose bearer authentication, and store the API key in the connection secret field.
See Zapier's remote MCP Client guide for the connection fields.
n8n
Use the private n8n node guide for Create Link and exact externalId lookup. The node uses an API-key credential and calls https://api.hoko.to. This is a private, self-hosted package; n8n Cloud and community publication are not included.
You can also use n8n's MCP Client or HTTP Request node. Set the URL to https://mcp.hoko.to for MCP, or call the REST operation routes with an Authorization: Bearer <HOKO_API_KEY> header. Keep the key in n8n credentials.
See n8n's MCP Client documentation for the node and credential fields.
Make
Use the private Make actions guide for Create Link and exact externalId lookup. For other operations, use Make's HTTP module with the unversioned Hoko route, add Authorization: Bearer <HOKO_API_KEY>, and store the key in a Make connection or secret variable. Make is documented here as a REST client, not as a native Hoko MCP host.
See Make's HTTP OAuth guide for the connection fields.
Custom MCP client
Configure Streamable HTTP with the canonical endpoint and bearer header:
{
"url": "https://mcp.hoko.to",
"headers": { "Authorization": "Bearer <HOKO_API_KEY>" }
}curl https://api.hoko.to/integrations/apps \
-H "Authorization: Bearer <HOKO_API_KEY>" \
-H "Accept: application/json"Use the same header for other Hoko operations. The OpenAPI document lists request and response schemas.
See the dedicated Custom API guide for client setup and resource route examples.
Catalog and connections
The Apps catalog contains reviewed provider metadata, channel information, availability, and setup guidance. An unavailable card is not an active integration and does not create a database record.
The connections API returns only grants that the signed-in human owns for the selected workspace. It includes the grant ID, verified client name, resource, scope labels, workspace, creation time, and effective status. It never returns access or refresh secrets.
API keys cannot read or manage human OAuth grants. A workspace administrator cannot inspect another person's connections. A registered grant with no current catalog card remains visible to its owner.
Connection states
Token expiry alone does not delete an authorization grant. Membership and client validity also affect the effective state.
OAuth host flow
The external host starts authorization and creates its own state and PKCE verifier. Hoko authenticates the human, shows the workspace and requested scopes, and issues a grant only after explicit consent.
The Apps dashboard can show setup instructions. It must not fabricate a callback URL, OAuth state, verifier, or connected account. Reconnecting starts a fresh consent flow. Changing workspaces requires a new grant.
Protected MCP calls use the registered OAuth resource and scope metadata. A host that needs account linking receives the standard OAuth challenge. Credentials stay outside tool arguments.
Disconnect
Removing Hoko access from one connection revokes that grant and its access and refresh credentials. Other devices, API keys, and independent grants remain active. Removing Hoko access does not delete an external host's past conversations or uninstall its application.
The dashboard action is Remove Hoko access.
Direct resource routes
Use these unversioned resource routes:
GET /integrations/apps
GET /integrations/apps/connections
DELETE /integrations/apps/connections/{grantId}The engine operation names are part of the adapter and MCP contracts.
The CLI reaches the same engine after browser login and workspace selection:
hoko auth login
hoko apps connections
hoko apps disconnect --grant-id <grant_id>Personal connection reads and removal require a Session Cookie or Human Token. API keys and delegated OAuth credentials cannot list or manage personal Apps grants.
Direct API and rate limits
Use API authentication for API keys and human access tokens. Use API rate limits to implement retry behavior. Respect Retry-After on 429 responses and check whether a write completed before retrying it.
Use the OpenAPI document for request and response schemas. The API is unversioned and keeps the existing resource paths.
Availability
An app card reports the current setup path and its requirements. Manual setup, host registration, provider approval, callback deployment, tool review, and public listing are separate steps. Availability does not grant additional permissions.