Functions

click.myinfrastructurePublished by myinfrastructure.clickOfficial publisherv1.0.3Updated Nov 4, 2026

Publicar e rodar funções, logs, variáveis e agendamentos

The publisher's own server: Auth

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Publishes and runs serverless JavaScript functions, with logs, variables and schedules, through a remote MCP endpoint.

What you can do
  • Publish and run serverless JavaScript functions, each deployed to its own endpoint
  • Read function logs and manage environment variables
  • Create and manage scheduled runs
  • Check account plan, function quota and active limits
When to use it
Useful when you want an assistant to deploy small JavaScript functions, inspect their logs, set variables or schedules, and check plan limits without leaving the chat. Suited to lightweight serverless work rather than full application hosting.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared. Functions are written as JavaScript modules with a default export taking request and context and returning a Response. An account with a plan and function quota is needed.
Before you install
Functions run code on the provider's infrastructure; outbound network access is closed by default and each function runs in its own isolate with time and memory caps. No tool deletes anything, so removing functions, schedules or variables must be done in the dashboard or REST API. Publishing and scheduling change live state.

Installation

In SourceWeft

  1. Open Functions in the dashboard and add it to a workspace.
  2. 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/click.myinfrastructure%2Ffunctions/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.

{
  "mcpServers": {
    "functions": {
      "type": "http",
      "url": "https://functions.manager.myinfrastructure.click/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.3LatestNov 4, 2026
  2. v1.0.1Oct 21, 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 listedRequired15 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.

Other Myinfrastructure integrations