Memory Bank MCP With Remote SSH Support 🧠

Created By
aakarsh-sasia year ago
MCP Server with Remote SSH support
Overview

What is Memory Bank MCP?

Memory Bank MCP is a Model Context Protocol (MCP) server designed for managing Memory Banks, enabling AI assistants to store and retrieve information across sessions, now with remote SSH support.

How to use Memory Bank MCP?

To use Memory Bank MCP, you can install it via npm and run it directly using npx. You can specify various options such as project path, folder name, and remote server details for SSH access.

Key features of Memory Bank MCP?

  • Memory Bank Management: Initialize, find, and manage Memory Banks
  • File Operations: Read and write files in Memory Banks
  • Progress Tracking: Track progress and update Memory Bank files
  • Decision Logging: Log important decisions with context and alternatives
  • Active Context Management: Maintain and update active context information
  • Remote Server Support: Store Memory Banks on a remote server using SSH

Use cases of Memory Bank MCP?

  1. Centralizing project memory for AI assistants
  2. Sharing Memory Banks among multiple users
  3. Maintaining persistent storage for project information

FAQ from Memory Bank MCP?

  • Can I use Memory Bank MCP without installation?

Yes! You can run it directly using npx.

  • What are the requirements for using remote server mode?

You need SSH access to the remote server and proper permissions to create/modify files.

  • How does Memory Bank MCP handle errors?

It has robust error handling to gracefully manage issues and continue operations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aakarsh-sasi
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago