Andish

ru.andishPublished by andish.ruv0.2.0Updated Oct 24, 2026

Knowledge-graph memory for your team's documents. Answers cite the source, not a summary.

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Andish gives an assistant knowledge-graph memory over your team's documents, with answers that cite the source rather than a summary.

What you can do
Connect an assistant to a team knowledge graph built from your documents, so it can recall and use that material in conversation. Answers are grounded in the source documents and cite them rather than returning a summary. The server runs locally and talks to the Andish service using your API key.
When to use it
Useful when your team keeps documents in Andish and you want an assistant to answer from them with traceable citations, rather than relying on general knowledge or unattributed summaries.
Requirements
Runs as a local process installed from the andish-mcp PyPI package, so Python is needed. Requires an Andish API key supplied in the ANDISH_API_KEY environment variable, created in the Andish dashboard. The ANDISH_BASE_URL variable is optional and defaults to the hosted service; set it only for your own deployment. Network access to the Andish service is needed.
Before you install
The server needs your Andish API key, which grants access to your team's document knowledge graph; keep it out of shared configuration and logs. Queries and document content are sent to the Andish service, so check that this fits your data-handling rules. Only change ANDISH_BASE_URL if you trust the endpoint you point it at.

Installation

In SourceWeft

  1. Open Andish 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

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.