NetClaw Gets Long-Term Memory: Community Contribution Brings MemPalace Integration

One of the most exciting aspects of open source is when the community steps up and adds capabilities you didn’t even know you needed. Today we’re thrilled to announce that NetClaw now has long-term memory — thanks to a fantastic contribution from community member Satyam Thakur.

The Memory Problem

AI agents are brilliant in the moment, but they forget everything between sessions. Ask NetClaw to troubleshoot a network issue today, and tomorrow it has no memory of what you discussed, what you tried, or what worked.

OpenClaw already had short-term memory through daily log files (memory/YYYY-MM-DD.md), but these are ephemeral — yesterday’s context fades as today’s work takes over.

Enter MemPalace: A Two-Layer Memory Architecture

The new integration creates a two-layer memory system:

Layer	Purpose	Technology
Short-Term	Daily session logs	OpenClaw’s existing `memory/YYYY-MM-DD.md` files
Long-Term	Persistent knowledge across sessions	MemPalace MCP with temporal knowledge graphs

What is a Memory Palace?

MemPalace uses a spatial metaphor inspired by ancient rhetoric techniques. Instead of a flat search index, memories are organized into a navigable structure:

Wings — People or projects (e.g., "datacenter-migration", "customer-acme")
Rooms — Specific topics within a wing
Halls — Memory types (facts, events, relationships)
Closets — Summaries for quick retrieval
Drawers — Original verbatim content

This architecture means NetClaw can now remember that "the BGP peer with AS65000 was flapping last month due to MTU issues" and recall that context when similar symptoms appear again.

19 Tools for Memory Management

The MemPalace MCP server provides 19 tools across five categories:

Palace Operations

Check memory status
List wings and rooms
Semantic search with filtering
Duplicate detection

Temporal Knowledge Graphs

Store facts with validity windows ("this was true from January to March")
Query what was true at a specific point in time
Track entity relationships over time
Generate timelines

Navigation

Traverse the knowledge graph across wings
Discover tunnels between related topics
Analyze connectivity patterns

Content Management

Add and organize memories
Delete outdated information

Agent Diaries

Per-agent continuous diaries using AAAK compression
Enables specialized expertise development over time

Why This Matters for Network Operations

Imagine these scenarios:

Recurring Issues: "This interface keeps flapping. Have we seen this before?"
NetClaw can now search its long-term memory and find that yes, this same interface had issues 6 months ago, and the root cause was a bad SFP.

Tribal Knowledge: "What’s the story with VLAN 100?"
NetClaw remembers that VLAN 100 was originally created for guest WiFi, was repurposed for IoT devices in Q2, and has special QoS policies because of that legacy camera system nobody wants to touch.

Change Context: "Why did we set the OSPF cost to 1000 on this link?"
NetClaw recalls the change request from 8 months ago where the link was deprioritized during a circuit migration that never got cleaned up.

Semantic Search Without API Calls

MemPalace uses ChromaDB for semantic search — meaning NetClaw can find relevant memories even when the exact keywords don’t match. Searching for "BGP problems" will find memories about "peering session failures" or "route convergence issues."

And it’s all local. No API calls to external services. Your network’s institutional memory stays on your infrastructure.

Community-Driven Innovation

This integration exists because Satyam Thakur saw an opportunity and contributed PR #55. The changes include:

MCP server registration in config/openclaw.json
Installation automation in scripts/install.sh
A comprehensive skill definition at workspace/skills/mempalace/SKILL.md
Documentation updates across README, TOOLS, SOUL, and AGENTS files

This is what open source is all about — the community identifying gaps and filling them with elegant solutions.

Getting Started

After updating NetClaw, the MemPalace MCP server is available immediately. NetClaw will automatically learn the memory protocol and AAAK dialect from status responses — no manual configuration needed.

Start building institutional memory by simply working with NetClaw. Over time, your AI network assistant will develop deep contextual knowledge about your specific environment, your historical decisions, and your operational patterns.

Thank you to Satyam Thakur for this contribution. NetClaw continues to grow through community involvement — now with long-term memory capabilities that transform ephemeral AI assistance into persistent institutional knowledge.

NetClaw Now Has Direct Access to Cisco’s Official Meraki and Catalyst Center API Documentation

Network automation with AI is powerful, but only when the AI has access to accurate, authoritative information. Today we’re excited to announce that NetClaw now integrates with Cisco’s official DevNet Content Search MCP server — giving our AI agent direct access to the source of truth for Meraki and Catalyst Center APIs.

The Problem with Guessing API Endpoints

When you ask an AI to help with Meraki or Catalyst Center automation, it typically relies on training data that may be outdated, incomplete, or simply wrong. API endpoints change. New features get added. Parameters get deprecated. The result? Code that doesn’t work, frustrating debugging sessions, and wasted time.

The Solution: Cisco-Approved MCP Integration

NetClaw now connects directly to Cisco DevNet’s official MCP server at https://devnet.cisco.com/v1/foundation-search-mcp/mcp. This means:

Always accurate — API documentation comes straight from Cisco, not from cached training data
Always current — As Cisco updates their APIs, NetClaw sees the changes immediately
Always complete — Full OpenAPI specifications including parameters, response schemas, and examples

What This Enables

Meraki API Search

Ask NetClaw about any Meraki capability and it will search Cisco’s official documentation:

"How do I configure L3 firewall rules?"
"What’s the API for VLAN management?"
"Show me the wireless SSID endpoints"
"How do I set up OAuth for Meraki?"

NetClaw returns the exact API endpoints, HTTP methods, required parameters, and example payloads — all from Cisco’s official documentation.

Catalyst Center API Search

The same applies to Catalyst Center (DNA Center):

"Find device inventory APIs"
"How do I automate policy deployment?"
"Show me assurance and health monitoring endpoints"
"What APIs handle site provisioning?"

Operation ID Lookup

For developers who know exactly what they need, NetClaw can lookup specific Meraki operations by ID and return the complete OpenAPI specification:

Lookup: updateNetworkApplianceFirewallL3FirewallRules

Returns: Full spec including path, method, all parameters, 
request body schema, response codes, and examples

Two New Skills

This integration adds two new skills to NetClaw’s arsenal:

Skill	Purpose
`devnet-meraki-search`	Search Meraki Dashboard API documentation
`devnet-catalyst-search`	Search Catalyst Center API documentation

No Authentication Required

The DevNet Content Search MCP is a public service — no API keys, no tokens, no setup. It just works.

Why This Matters

This isn’t just another integration. This is NetClaw getting authoritative access to Cisco’s own documentation. When you ask NetClaw about Meraki or Catalyst Center APIs, you’re not getting guesses based on training data — you’re getting answers sourced directly from Cisco DevNet.

The result: more reliable automation, fewer errors, and faster development cycles.

Get Started

NetClaw 71 MCP integrations now include DevNet Content Search. Just ask:

"Search Meraki API for firewall rules"

"Find Catalyst Center device inventory endpoints"

"Lookup the Meraki operation createNetworkMerakiAuthUser"

NetClaw will search Cisco’s official documentation and return exactly what you need.

NetClaw continues to grow — now with 162 skills backed by 71 MCP integrations, bringing authoritative network automation to your fingertips.