Connection preview — sign-in, action/source reads and credit visibility are available. Creating, building, publishing and running actions are not enabled yet.

Your actions.
Your agent.

Create JavaScript or Python actions, add libraries, test with sample data and run published actions. Everything stays in the same Turbyn workspace as your web app.

No additional MCP fee. Connections and tool requests are free. Building, testing and running code use your existing allowances and credits.

Connect to Turbyn

  1. Open your client's remote MCP or custom connector settings. The client must support remote HTTP MCP and OAuth.
  2. Add this server URL:https://mcp.useturbyn.com/mcp
  3. Sign in to Turbyn, choose your workspace and review the requested permissions. Grant publishing, production execution or secret access only when needed.
  4. Return to your client. Check connection settings for confirmed activity or to revoke access.

Client labels and supported features vary. A saved URL alone does not mean the connection is authenticated.

Try your first action

Show my Turbyn workspace, list its actions and tell me my remaining credits and included build minutes. Do not make any changes.

You can also ask for Python, npm or Python libraries, complete source files, typed outputs and permitted secret bindings. Publishing is a separate authorized step.

Files, secrets and connected accounts

Paste source text directly, or use the file-transfer flow supported by your client. A file attached to a chat or a path on your computer is not automatically uploaded to Turbyn. Project paths are relative to the action, such as src/main.py.

Existing secret values cannot be read back through MCP. Enter sensitive values in Turbyn and let the agent bind them by name. Account connections, payment and workspace membership are managed in the web app.

If a connection fails

Check that you used the complete endpoint above, finished browser authorization and selected the correct workspace. For expired or revoked access, reconnect from your client. For a pending build or run, ask the agent to check its operation ID; reconnecting does not require starting the work again.