What it does

Ask questions such as “Which projects need attention?”, “Show me the stack for GoodHitch”, or “Did any Vercel deployment fail?” BindDock answers from its controlled, owner-scoped application data rather than exposing a general-purpose route to provider APIs.

Read only by design. MCP V1 cannot launch a stack, resume a Supabase project, deploy, send email, change DNS, write environment variables, disconnect an account, or delete anything.

Available tools

AI

list_projects

List your BindDock projects, completeness, linked roles, and overall state.

AI

get_project_stack

Explain the provider resources linked to one project and what is missing.

AI

get_needs_attention

Return current, actionable infrastructure and authorization issues.

AI

get_connections

Summarize connected accounts, effective permissions, and freshness.

AI

get_activity

Return recent sanitized activity with its current actionable or resolved relevance.

AI

get_infrastructure_health

Answer compact questions such as “Is anything broken?”

Authentication and privacy

A compatible client discovers BindDock's OAuth 2.1 metadata, uses authorization code flow with PKCE, and asks you to approve read-only access in BindDock. Every access token is audience-bound to the MCP endpoint and maps to exactly one BindDock user. Database row-level security continues to enforce owner isolation.

MCP responses never include provider access or refresh tokens, API keys, secret keys, environment-variable values, authorization headers, encrypted credentials, encryption material, or raw provider responses. BindDock does not store your AI prompts or conversations.

Historical Activity remains unchanged. When deciding whether an old failure still needs action, BindDock uses current monitoring and Needs Attention state rather than the event's age or status alone.

Connect a compatible AI client

  1. Open your AI client's tools, connectors, or MCP settings.
  2. Add a remote Streamable HTTP MCP server.
  3. Enter https://www.binddock.com/mcp.
  4. Sign in to BindDock and approve the read-only authorization.
  5. Ask the client to list your BindDock projects or check infrastructure health.

Then ask naturally:

  • Is anything broken?
  • Show me my projects.
  • Show me the stack for GoodHitch.
  • Are any databases paused?
  • Are any domains expiring?
  • What changed recently?

Menu names vary by client, and remote custom MCP support may depend on the client, account, or workspace plan. BindDock does not claim a public marketplace listing or an official ChatGPT, Codex, Claude, or Cursor integration. Use only clients that support authenticated remote Streamable HTTP MCP servers.

Beta status

MCP V1 is in public beta. Tool names and response details may evolve, while the read-only boundary and secret-redaction guarantees remain core constraints. Questions, bugs or beta feedback? Email contact@binddock.com.

Create a BindDock accountReview security