Skip to content
v0.2.0Apache-2.0

Put your MCP server on Authflow: free or paid access through one OAuth sign-in, with the agent doing the setup. Connects the Authflow management and docs MCPs and adds onboarding skills.

integrate-origin

Implement Authflow's Origin Protocol in an MCP server so it accepts requests forwarded by the Authflow gateway - pick the dotnet, typescript, python, or proxy integration, apply the resource-specific integration plan, and get the fail-closed rules right. Use when changing an MCP server's code for Authflow, or when an origin fails verification.

onboard

Put an MCP server on Authflow end to end - create the resource, integrate the Origin Protocol, deploy, connect Stripe for paid access, verify, and publish. Use when the user wants to add sign-in, a paywall, subscriptions, or usage billing to their MCP server with Authflow, or wants to resume an Authflow setup that is partly done.

operate

Run a live Authflow MCP - read usage and earnings, rename the workspace or MCP, change price or metering and republish, and disable an MCP. Use for day-to-day management of MCPs already on Authflow.

origin-key

Deliver an Authflow origin API key into a secret store with the authflow CLI, for paid MCPs that use origin_reported metering. Only use when the resource is paid with metering_mode origin_reported and the origin needs AUTHFLOW_ORIGIN_API_KEY; free and gateway-metered MCPs never need a key.

pricing

Choose an Authflow MCP's offer - free or paid, monthly price and credits, gateway metering versus origin-reported usage, and per-tool costs. Use when creating or changing an Authflow resource's access mode, price, credits, metering_mode, metering_default_units, or tool_units.

test-as-consumer

Test a published Authflow MCP the way a consumer will - connect a separate MCP client to the gateway URL, sign in, complete sandbox checkout for paid MCPs, call tools, and check usage and earnings. Use after publishing, or when the user wants to confirm an Authflow MCP works end to end.

troubleshoot

Diagnose why an Authflow MCP will not verify, publish, connect, or bill - pending_requirements, resource_not_ready, 403 invalid_origin_identity, usage endpoint errors, management sign-in failures, and Stripe readiness. Use when an Authflow tool returns an error or a requirement will not clear.