Vibe

il.co.vibecontrolPublished by vibecontrol.co.ilOfficial publisherv1.0.0Updated Nov 7, 2026

Landing pages, mailing lists, signup forms and email campaigns in Vibe

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Vibe server that lets an assistant work with landing pages, mailing lists, signup forms and email campaigns.

What you can do
  • The registry description says it covers landing pages, mailing lists, signup forms and email campaigns in Vibe.
  • No tool list, instructions or README are supplied, so the specific actions available to an assistant are not documented here.
  • Expect it to relate to building and managing marketing pages, collecting signups and running email campaigns.
When to use it
Consider it if you use Vibe for marketing pages, signup forms or email campaigns and want an assistant to work with that content directly.
Requirements
A remote endpoint at the provider's site; no local package or runtime is needed. Authentication is OAuth and required, so you need a Vibe account that can authorize the connection. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to your Vibe account, so review the scopes requested during authorization. The server likely touches signup forms, mailing lists and email campaigns, which can involve subscriber data and sending messages to recipients; confirm what it can change or send before use. No tool list is published, so its exact write capabilities are unknown.

Installation

In SourceWeft

  1. Open Vibe 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/il.co.vibecontrol%2Fvibe/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": {
    "vibe": {
      "type": "http",
      "url": "https://www.vibecontrol.co.il/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.0LatestNov 7, 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.