Utplava

io.github.kp080681Published by GitHub account kp080681v1.0.0Updated Oct 29, 2026

Put AI-built apps online from GitHub: deploy, check status, read logs and set env vars.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Utplava is a remote MCP server that lets an assistant deploy AI-built apps from GitHub, check deployment status, read logs and set environment variables.

What you can do
  • Deploy apps built with AI directly from a GitHub repository
  • Check the status of deployments
  • Read deployment logs
  • Set and manage environment variables for deployed apps
When to use it
Useful when you build or generate an app with an assistant and want to publish it without leaving the conversation, then monitor the deployment and adjust its configuration.
Requirements
A remote endpoint at app.utplava.dev reached over streamable HTTP; OAuth sign-in is required. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your account, and deployments publish apps publicly and change live configuration. Setting environment variables may involve secrets; review what is written before approving. Logs and repository content are sent to the Utplava service.

Installation

In SourceWeft

  1. Open Utplava in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.kp080681%2Futplava/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "utplava": {
      "type": "http",
      "url": "https://app.utplava.dev/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.