Let agents drive the flow API over MCP

The engine now speaks MCP at /mcp, with a built-in OAuth 2.1 authorization
server in front of it: an agent registers itself, sends a human to the browser
to approve it, and exchanges the resulting code for a token. PKCE is required,
codes are single-use and stored only as hashes, the browser is redirected to
the URI that was registered rather than the one asked for, and refresh tokens
rotate so that replaying a spent one revokes the whole line.

Twenty tools cover reading, building, publishing and running flows, and each
one calls the same REST endpoint the dashboard calls, in-process, carrying the
caller's own token. That keeps one description of what a flow is and what may
be done to it — validation, the draft/publish split, the version check — and
means an agent can do nothing a person could not do in the browser.

Agent tokens are RS256 with a keypair of their own rather than the secret that
signs browser sessions, so deleting the key withdraws every agent without
logging anyone out, and deps.decode_token grew the branch that trusting a
second issuer will need when the hosted login arrives.

This commit is contained in:

Melvin Strobl

2026-08-16 00:22:41 +02:00

parent cb5e8f0ecc

commit 6d2e25c2ca

28 changed files with 2459 additions and 555 deletions

									
										.env.example
									
		+3
		
												View File
												
				@@ -48,3 +48,6 @@ SENTRY_DSN=

				# Docker registry images

				DOCKER_IMAGE_BACKEND=fluksio-backend

				DOCKER_IMAGE_FRONTEND=fluksio-frontend

				# The MCP endpoint agents connect to, and the OAuth server behind it.

				MCP_ENABLED=true