Invoker

page.invokerPublished by invoker.pagev0.1.1Updated Oct 24, 2026

Deploy forms and sites to live URLs from AI conversations with automatic form capture.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Invoker is a local MCP server that lets an assistant deploy forms and sites to live URLs from an AI conversation, with automatic form capture.

What you can do
Deploy forms and sites to live URLs directly from an AI conversation, with forms captured automatically. The manifest lists no tools, so the exact operations are not documented; the description indicates publishing forms and sites to hosted addresses.
When to use it
Useful when you want an assistant to publish a form or a small site to a live URL without leaving the conversation, and want submitted form data captured automatically.
Requirements
Runs as a local process on the user's machine via the npm package invoker-mcp over stdio. Desktop only; not executable on the web. No authentication, environment variables or headers are declared.
Before you install
It publishes content to live public URLs, so anything deployed becomes reachable by others. Automatic form capture means submitted data is collected; check where that data is stored and who can access it before deploying.

Installation

In SourceWeft

  1. Open Invoker in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

15% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.