Guide

Govern

AI clients (MCP)

2 min readOpen in Neblex

Any AI client that speaks the Model Context Protocol (for example Claude Code, Codex, Cursor, VS Code or Windsurf) can build and operate in your workspace on your behalf, under the same rules as you. The client receives operating instructions and a described tool catalog when it connects, so it uses the real building blocks instead of guessing.

Connect an AI client

  1. Add the endpoint to your client. The address is https://if.neblex.com/mcp. For example in Claude Code: claude mcp add --transport http neblex https://if.neblex.com/mcp.
  2. Authorize in the browser. On first use the client opens your sign-in. Complete two-factor, then choose on the consent screen the scopes (operate, author, publish), the projects or flows it may reach and the environment it works in, and Authorize.
  3. Build. Your client validates before saving, tests before publishing, and hands you a link whenever a person must enter a secret or approve a protected change. Publishing into a protected environment waits for a human approval.

Connected clients are listed under API Consumers › Connected AI Clients with who granted them; Revoke cuts access at once. Using MCP requires the Use MCP channel in your permission profile.

Scope what the assistant may touch. Building and publishing always need a user-approved sign-in with a second factor. A static API consumer key used with MCP can only inspect and run its granted flows; it can never create or publish.

What your assistant can do

ToolsScopeWhat they do
get_platform_capabilities, get_*_schemareferenceWhat can be built, the safe order of work and exact shapes of flows, forms, apps, tables and agents.
list_flows, get_flow, run_flow, get_run, flow_healthoperateRead and run granted flows and check results and health.
list_connectors, list_node_kinds, describe_connector, list_connectionsoperate / authorDiscover systems, nodes and operations. Secrets are never returned.
validate_flow, create_flow, update_flow, test_flowauthorBuild and test flows.
Form, app, data table and agent tools; version and restore toolsauthorBuild the other parts of a solution and use their history.
create_connectionauthorCreates a connection without secrets and returns the link where a person enters them.
publish_flow, publish_form, publish_app, publish_agentpublishTake things live or offline, with approval where required.