Wikivibe MCP

io.github.AlexMi64Published by GitHub account AlexMi64v0.1.0Updated Oct 24, 2026

Search and read public Wikivibe articles about AI coding, agents, MCP, GEO, bots and deployment.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & MemoryMedia & Design

Overview

AI-generated overview

A public read-only remote MCP server that lets an assistant search and read Wikivibe articles on AI coding, agents and MCP, plus VibeDesign templates.

What you can do
Search public Wikivibe articles by query and read a single article by URL, path, section and slug, in Russian or English, covering AI coding, agents, MCP, SEO/GEO, bots and deployment. List the newest canonical articles and the public sections that contain indexable articles. Search the public VibeDesign catalog of templates, layouts, components, dashboards, animations and source links, and read one template by slug, URL or localized path.
When to use it
Useful when you want an assistant to look up or summarize Wikivibe's public material on AI coding, agents, MCP, bots or deployment, or to find ready-made design templates with source links, without leaving the chat.
Requirements
A remote Streamable HTTP endpoint; no account, API key or environment variable is declared. Clients that support remote MCP servers can connect directly, and clients needing a local proxy can run the mcp-remote package via npx, which requires Node.js and network access.
Before you install
Read-only by design: it cannot edit, publish, access CMS or private user data, run commands or call external APIs on the user's behalf. Content is limited to public canonical articles and approved templates, so drafts and non-indexed material are unavailable. Queries and requested paths are sent to the third-party Wikivibe service.

Installation

In SourceWeft

  1. Open Wikivibe MCP 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/io.github.AlexMi64%2Fwikivibe-mcp/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": {
    "wikivibe": {
      "type": "http",
      "url": "https://wikivibe.ru/mcp/"
    }
  }
}

README

Wikivibe MCP

Wikivibe MCP is a public read-only Model Context Protocol server for Wikivibe, a Russian/English knowledge base about AI coding, vibe coding, AI agents, MCP, developer tools, SEO/GEO, Telegram bots, integrations, databases and deployment workflows. It also exposes the public VibeDesign catalog of ready-made templates, layouts, components, dashboards, animations and source links.

The server gives AI assistants and agentic IDEs structured access to public Wikivibe articles and approved design templates. It does not expose private data, drafts, user profiles, comments, analytics, CMS records, credentials or write operations. The endpoint only returns canonical, indexable public materials that are already available on the website.

Remote MCP endpoint

Tools

The hosted server exposes six tools:

  • search_articles - search public canonical Wikivibe articles by query.
  • get_article - read one public article by URL, path, section and slug.
  • list_latest_articles - list the newest public canonical articles.
  • list_sections - list public sections that contain indexable articles.
  • search_design_templates - search public VibeDesign ready-made templates, layouts, components, dashboards, animations and source links.
  • get_design_template - read one public VibeDesign template by slug, URL or localized path.

Example client config

For clients that support remote Streamable HTTP MCP servers, use:

json
{  "mcpServers": {    "wikivibe": {      "url": "https://wikivibe.ru/mcp/"    }  }}

For clients that need a local proxy, use mcp-remote:

json
{  "mcpServers": {    "wikivibe": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://wikivibe.ru/mcp/"]    }  }}

Example prompts

  • Search Wikivibe MCP for articles about MCP in AI development and summarize the best source.
  • Open the Wikivibe article about connecting a website to AI agents and explain the practical value.
  • List latest Wikivibe articles about AI coding tools, agents and deployment.
  • Find Russian VibeDesign dashboard templates with GitHub source links and return the best options.
  • Open a VibeDesign template page and explain what source, demo and preview assets are available.

Safety model

Wikivibe MCP is intentionally read-only. It cannot edit content, publish articles, access CMS data, read private user data, run commands, call external APIs on behalf of a user, or mutate any server state. It is a discovery and reading interface for public knowledge base content and public design-template metadata.

Contact

For listing, verification or integration questions: [email protected]

Source: README.md at commit a04cca9

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% 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

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

  • Auth declaredRequired10 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
  • Documentation15 pts
  • License10 pts