Yandex360 Mcp

io.github.pa1chPublished by GitHub account pa1chv0.2.0Updated Oct 24, 2026

MCP server for Yandex 360 services (Wiki, and more) — tools for AI assistants.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server that connects AI assistants to Yandex 360 services, starting with Yandex Wiki, through dedicated tools.

What you can do
Provides tools that let an assistant work with Yandex 360 services, with Yandex Wiki named as the first supported service. The registry description gives no tool list, so the exact operations available are not documented here. It runs as a local process over stdio rather than as a hosted endpoint.
When to use it
Consider it when you use Yandex 360, especially Yandex Wiki, and want an assistant to reach that content from a local MCP client. Check the project's own documentation first, since the available tools are not described in the registry entry.
Requirements
A local Python environment able to install the yandex360-mcp package from PyPI, and an MCP client that launches local stdio servers. No environment variables, headers, or authentication method are declared, so how it signs in to Yandex 360 is not stated.
Before you install
The server works with a Yandex 360 account, but the registry entry declares no authentication, so it is unclear what credentials it needs or where they are stored. No tool list is published, so you cannot tell from this entry whether it only reads data or can also change or delete it. Review the project's source and documentation before connecting a real account.

Installation

In SourceWeft

  1. Open Yandex360 Mcp 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.2.0LatestSep 16, 2026

Score

25% 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
  • 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.