ChatGPT Plugin

KamuiDash

Manage apps on KamuiDash

Brand: Unknown

Category: Pending
Primary Subcategory: Pending

Integration details

Description

KamuiDash helps you manage the apps you own on KamuiDash. Inspect projects, apps, deployment status, and logs. With your explicit confirmation, create and update apps, create databases, or configure custom domains.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-10-21
Tool count: 15
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce KamuiDash has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

15 tools agents can invoke

Creates a new dynamic web server app (Go, Node.js, Python, or Ruby) from a connected GitHub repository, provisions it in the selected KamuiDash project, and deploys the selected branch. This changes external state, publishes the app, and provisions a billable resource whose cost depends on the selected spec/plan. Only call this after the user has selected the project, repository, branch, and app spec and confirmed any applicable cost. Prerequisites: call list_projects for project_id, and list_repositories for organization_name/owner_type/repository_name (and list_branches for repository_branch); if list_repositories returns a 'user_instruction', relay it and stop until the user confirms. If database_id is provided, KamuiDash connects the app to that database and injects DATABASE_URL automatically; do not pass DATABASE_URL (or other secrets) in env_vars.
create_app
Creates a new PostgreSQL database in the selected KamuiDash project. This changes external state and provisions a billable resource whose cost depends on the selected spec/plan. Only call this after the user has selected the project, database name, and spec and confirmed any applicable cost. Prerequisites: call list_projects to get the project_id. The database name must be unique within the project; during the Free Trial a project can hold at most 1 database. Provisioning is asynchronous; the database becomes ready a short time after this returns.
create_database
Creates an empty project in the user's connected KamuiDash account to group apps and databases in the selected region. It saves the project and its selected free or pro plan and provisions the project's namespace. This tool does not deploy apps, provision databases, collect payment details, or execute a payment. It does not upgrade an existing project's plan. Use list_projects to check existing projects first. Only call this after the user has selected the name, region, and plan and explicitly approved project creation with an understanding of the applicable limits. The free plan allows one free project per user. Returns the new project_id.
create_project
Creates a new static web page app (HTML/CSS/JS site or SPA) from a connected GitHub repository, provisions and publishes it in the selected KamuiDash project. This changes external state, publishes the app, and provisions a billable resource whose cost depends on the project plan. Only call this after the user has selected the project, repository, and branch and confirmed any applicable cost. Prerequisites: call list_projects for project_id, and list_repositories for organization_name/owner_type/repository_name (and list_branches for repository_branch); if list_repositories returns a 'user_instruction', relay it and stop until the user confirms.
create_static_app
Read-only. Retrieves details for the specified application: app type, spec, URL, custom domain, GitHub repository info, language type, and status. Use get_project first to find the app_id. Does not change any state.
get_app
Read-only. Retrieves recent runtime logs for the specified application. Output is truncated to the most recent entries and secret-like values are masked before being returned. Does not change any state.
get_app_logs
Read-only. Retrieves the build/deploy logs for a specific deployment run. Output is truncated to a recent window and secret-like values are masked before being returned. Use list_deploy_runs first to get the available run_id values. Does not change any state.
get_deploy_run_logs
Read-only. Retrieves details for the specified project: plan type, region, status, and a summary of its apps and databases. Use list_projects first to get the project_id. Does not change any state.
get_project
Lists the branches of a GitHub repository accessible via the KamuiDash GitHub App. Use this to get a valid repository_branch value for create_app/create_static_app. The owner is the organization name or username returned by list_repositories. It does not change any project, app, database, or domain, but it does refresh the caller's own cached list of GitHub App installations, which writes to KamuiDash.
list_branches
Read-only. Lists recent deployment runs for the specified application. Returns run_id, status, start timestamp, and commit info for each deployment. Use the run_id with get_deploy_run_logs to see detailed logs for a specific deployment. Does not change any state.
list_deploy_runs
Read-only. Retrieves all projects owned by the user. Each project contains apps and databases. Use this first to get the project_id before creating or deploying apps. Does not change any state.
list_projects
Lists the GitHub repositories the user can deploy from (those where the KamuiDash GitHub App is installed), with each repository's owner, owner_type, and name. Call this before create_app / create_static_app to obtain valid organization_name, owner_type, and repository_name (use list_branches for repository_branch). When no repositories are connected, the response's 'repositories' is empty and it includes 'github_app_install_url' and a 'user_instruction' field describing how the user connects a repository. It does not change any project, app, database, or domain, but it does refresh the caller's own cached list of GitHub App installations — which writes to KamuiDash — so a repository connected moments ago shows up. Results are paginated; pass next_cursor back as cursor until it is absent, even when a page is empty.
list_repositories
Registers or replaces the custom domain for an existing app and returns the DNS records the user must create at their DNS provider. This is destructive: it may replace the app's previous custom domain (the old one is removed). Only call this after the user has selected the app and explicitly confirmed the domain to attach. Prerequisites: call list_projects / get_project to get project_id and app_id. On success it returns host_key + host_value (a TXT record for domain-ownership and SSL validation) and cname; the domain goes live after the user creates those records at their DNS provider and validation finishes (ssl_status reflects progress).
set_app_custom_domain
Updates the settings of an existing web server app connected to a GitHub repository, and redeploys it. This is a partial update: only the fields you pass are changed and every field you omit keeps its current value (an empty string counts as 'not passed', so this tool cannot clear a command — that is done on the KamuiDash dashboard). This changes external state and starts a new deployment that can change or break the running app; changing replicas or app_spec_type also changes the size of the billable resource. Only call this after the user has reviewed and explicitly approved the change, and confirmed any applicable cost when the size changes. Prerequisites: call list_projects / get_project for project_id and app_id. This tool is for GitHub-connected web server apps: an app created from uploaded files, or a static web page, is updated elsewhere (use update_static_app for a GitHub-connected static web page).
update_app
Updates which GitHub repository, branch, or directory an existing static web page is published from, and republishes it. This is a partial update: only the fields you pass are changed and every field you omit keeps its current value (an empty string counts as 'not passed'). This changes external state and starts a new deployment that can change or break the published site. Only call this after the user has reviewed and explicitly approved the change. Prerequisites: call list_projects / get_project for project_id and app_id, and list_repositories / list_branches when changing the repository or branch. This tool is for static web pages published from a GitHub repository: a site created from uploaded files is updated elsewhere, and a web server app uses update_app.
update_static_app

FAQs

KamuiDash ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve KamuiDash's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.