Connect your AI to BlinkHost

BlinkHost MCP lets an AI assistant use your BlinkHost workspace through scoped tools. It can inspect account capabilities, manage permitted projects, start eligible Idam work, review releases, and hand an immutable Git revision to BlinkHost's build pipeline. Your assistant supplies its own model; calling Idam also uses BlinkHost AI credits.

Connect

Use the remote Streamable HTTP endpoint:

https://mcp.blinkhost.me/mcp

Add BlinkHost in your assistant's MCP settings and choose its sign-in action. The browser opens BlinkHost, where you can sign in or create an account, verify your email, and return to consent. You do not need to create an account before discovering the server. Signup still takes place in the BlinkHost browser flow. If signup takes longer than the authorization window, return to your assistant and reconnect.

Review the app name and return address. Dynamically registered apps display Unverified app because registration does not verify the publisher. Select one workspace, explicitly choose selected projects or all projects, then choose permissions, expiry and the Idam task ceiling. All-project access includes future projects. Creating projects requires all-project access and the project-creation permission. A connection cannot silently gain access to another workspace.

The hosted service uses JSON-RPC 2.0 and OAuth with PKCE. It does not provide a local executable or a standalone legacy SSE URL. Client configuration examples below describe supported vendor configuration formats; successful signed-in qualification is tracked separately. Marketplace discovery and account eligibility vary by product.

Coding agents

Codex

codex mcp add blinkhost --url https://mcp.blinkhost.me/mcp
codex mcp login blinkhost

Or merge this TOML configuration into your Codex configuration. Complete the browser consent, then ask Codex to read your BlinkHost account context. See Codex MCP documentation.

Claude Code

claude mcp add --transport http --scope user blinkhost https://mcp.blinkhost.me/mcp

Open Claude Code, run /mcp, select BlinkHost and authenticate. A project configuration is also available. See Claude Code MCP documentation.

Cursor

Merge the Cursor configuration into .cursor/mcp.json for your project or the global MCP configuration. Open Customize/MCP, enable BlinkHost and complete OAuth. See Cursor MCP documentation.

Antigravity

Merge the Antigravity configuration into the configuration shown by its MCP manager. Current versions use ~/.gemini/config/mcp_config.json globally or .agents/mcp_config.json per workspace. The remote URL field is serverUrl. Select BlinkHost in the MCP manager and authenticate. See Antigravity MCP documentation.

VS Code / GitHub Copilot

Merge the VS Code configuration into .vscode/mcp.json, start the server from the MCP command menu and complete its sign-in flow. This describes interactive VS Code; GitHub's unattended cloud coding agent has separate authentication restrictions. See VS Code MCP documentation.

Merge entries into existing files instead of overwriting your other servers. These files contain the endpoint only. Do not paste BlinkHost dashboard tokens, passwords or client secrets into them. Automatic registration must be enabled by BlinkHost for URL-only OAuth setup. If your client reports registration unavailable, contact support with its product/version and the displayed callback address; do not guess a callback or use a wildcard.

ChatGPT, Claude and other hosted assistants

Where your account supports custom remote MCP connections, add the same endpoint and follow the product's OAuth flow. ChatGPT app publication and Claude connector directory approval are separate from manual connection. A public URL or a registry entry does not mean BlinkHost is already listed or recommended in either product. Hosted callbacks must be qualified independently from local coding agents.

For Gemini, Muse, enterprise assistants and automation tools, check that product's current custom connector and OAuth requirements with support. Do not assume every product accepts an arbitrary MCP URL or that a local integration also works in its cloud agent.

Start with your account's actual capabilities

Try: “Read my BlinkHost account context, list the projects I allowed, and explain which deployment options my plan supports.”

The agent should read account_context before proposing resources and idam_capabilities before using Idam. These report current availability and limits where available; unknown information must not be treated as unlimited or zero. Live server checks enforce membership, plan, credits, permissions and resource eligibility when work is admitted. Workspace-wide credit information can be visible with account-read permission even when project access is selected.

The BlinkHost delivery skill gives compatible agents the workflow guidance. Installing a skill does not grant account access; OAuth permissions remain separate.

Build from your agent's source code

An external coding agent can develop the application in your repository using your existing Git provider permissions. Connect that repository to your BlinkHost project through Project settings → Source control. MCP does not grant GitHub repository-write permission.

1. Check the supported runtime and plan, choose an authorized project and connect its repository.
2. Commit and push your application using your normal Git tools. Allow BlinkHost to ingest that revision.
3. Call list_source_snapshots for the project. Use the returned immutable snapshot ID, commit SHA, tree digest and eligible environment ID.
4. Call prepare_source_build with those exact values and a new client_request_id. Read the returned review URL and approve in BlinkHost.
5. Poll get_operation, then get_source_build. Successful native builds automatically request deployment to the reviewed environment. Review therefore authorizes the build and its downstream deployment request, which can consume platform resources.
6. Inspect deployment status and verify the expected live application behaviour. A queued job, build success or deployment ID alone is not proof that it serves correctly. The source status tool explicitly returns serving_verified: false; your agent must perform the live check separately.

If Git auto-deployment is enabled, pushing can already schedule a build. Inspect the returned automatic-build warning and existing build status before starting another one. New source tools require builds:read and builds:execute; existing connections need a new OAuth consent to add these permissions.

This path uses BlinkHost's existing runtime and build isolation. It does not provide persistent customer containers, arbitrary shell execution or general-purpose source upload through MCP. Eligible Idam workflows provide an alternative build path and require their own credit and source/release reviews.

Change or revoke access

Open Settings → AI connections. Use Edit access to remove projects or permissions, shorten expiry or lower the task ceiling. Narrowing applies to subsequent calls using existing tokens; already admitted work is not automatically cancelled. Grant changes invalidate outstanding browser reviews.

Adding projects, selecting all projects, extending expiry or increasing the task ceiling requires an explicit review of the broader grant. Adding action permissions requires reconnecting from the AI client so it requests them through OAuth. Access history records changes and revisions. Revoking the connection prevents further authorized calls and refresh. Reconnect for a different workspace, subject to your client's support for multiple connections.

The ceiling is per Idam task, not a daily or monthly connection budget. Existing wallet and workspace budgets also apply. Connections expire in 1–90 days; access tokens last 15 minutes and refresh tokens rotate. Clients should serialize refresh requests.

Recover interrupted work

Every write uses a stable UUID client_request_id. Retain it and the identical arguments when retrying the same intended operation. After a lost response, read get_operation if you have the operation ID, or repeat the original request with the same request ID. A new UUID represents new work and can incur another charge.

For help, email support@blinkhost.me with your client/version, UTC time, operation ID and error code. Where the client exposes MCP result metadata, include blinkhost/support_reference. Do not include access tokens, passwords, private source or prompts. Read the Privacy Policy and legal documents for processing and terms. Your AI provider's handling of tool results also applies.