MCP.Market

Waggle MCP server

by Abhigyan-Shekhar·io.github.Abhigyan-Shekhar/Waggle-mcp·v0.1.8·44 stars

Persistent graph-backed conversational memory for AI agents.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

44 stars

Reviews

Write one

Nobody has reviewed Waggle yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Waggle tools (1, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • delete_nodewrite action

    Delete a node and all connected edges from persistent memory.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan71 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Waggle compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
100%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
44
more than 93% of 28,688 servers

What its tools let an agent do: 1 delete

Install Waggle in Claude Code, Cursor or VS Code

claude mcp add Waggle-mcp -- uvx waggle-mcp
Add to Cursor

What the publisher says

From the Waggle repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.Abhigyan-Shekhar/Waggle-mcp -->

Project memory for humans and AI agents. Keep decisions, context, and the reasons behind them across conversations.

Install Waggle · Try the browser workspace · Documentation

Keep the context, not just the conversation

Waggle is an open-source, local-first memory layer for AI agents. It stores project knowledge as a graph: what you decided, why it matters, what it depends on, and what has changed. Your next conversation can pick up from that context instead of starting over.

Use Waggle with your MCP client, inspect and edit memory in Graph Studio, or bring a portable memory graph into the browser workspace.

and open questions without repeatedly pasting context.

  • Continue across sessions. Recall project decisions, requirements, preferences,

contradictions, and the history behind a decision.

  • Understand the reasoning. Explore relationships, supporting evidence,

humans approve the exact content before it becomes authoritative.

  • Keep control of corrections. In the WebMCP workspace, agents propose changes;

workflows without tying your graph to one client.

  • Take memory with you. Export and import .abhi files across supported

does not require a Waggle account or an external database.

  • Start locally. The default SQLite store lives on your machine. Local use

Quick Start

The Python package requires Python 3.11+ and pipx. On macOS, you can install pipx with brew install pipx; see the installation guide for client-specific options.

pipx install waggle-mcp
pipx ensurepath

Restart your terminal after the first pipx ensurepath, then run:

waggle-mcp setup --yes
waggle-mcp doctor

Restart your MCP client to load Waggle. Setup detects supported clients and writes their configuration; automatic memory behavior uses the client's installed hooks, skills, or project instructions.

To check continuity, ask your agent to remember a project decision, then open a fresh session in the same project and ask what was decided. Keep the same project identifier across sessions.

Choose your client

For clients that accept an mcpServers configuration:

{
  "mcpServers": {
    "waggle": {
      "command": "waggle-mcp",
      "args": ["serve", "--transport", "stdio"]
    }
  }
}

If the command is not found, run pipx ensurepath and reopen your terminal. Use the troubleshooting guide for installation, startup, and client connection issues.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Waggle: common questions

Is Waggle MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Waggle safety report
How do I install Waggle?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Waggle need an API key?
No secret keys are declared. It reads 5 settings from the environment.
Is Waggle maintained?
The last commit was 40 days ago (2026-09-25). The latest release is v0.1.8.
What can I use instead of Waggle?
Servers from other publishers that do the same job: State Memory MCP server, Codebase Memory MCP server and Neo4j Memory MCP server. Compare all Waggle alternatives.
How does Waggle compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Waggle

Same job from other publishers: the closest match first, then the best rated.

All Waggle alternatives →
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Codebase Memory
    Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
    C
  • Neo4j Memory
    MCP Neo4j Knowledge Graph Memory Server
    A
  • Knowl
    Persistent memory for AI agents, for code, research and everyday life. Stale facts retire.
    A