Skip to main content
Glama
memwyreai

Memwyre

Official
by memwyreai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMWYRE_API_KEYYesYour Memwyre API key. Generate from the Memwyre Dashboard.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_memwyreA
Search your Memwyre knowledge base and persistent memories using hybrid semantic search.

Args:
    query: The natural language search query or topic to look up.
    limit: Maximum number of relevant memories to return (default 5).
save_memoryA
Save a new memory snippet, note, bug fix, or architecture decision to your Memwyre knowledge vault.

Args:
    content: The technical content, note, pattern, or decision to save.
    tags: Optional list of tags for organization (e.g. ['architecture', 'auth', 'database']).
    title: Optional title for the memory note.
list_memoriesB
List recent memories and notes from your Memwyre vault.

Args:
    limit: Number of memories to return (default 10).
    skip: Offset for pagination (default 0).
get_documentA
Retrieve the full content of a specific document or memory by its ID.

Args:
    document_id: The integer ID of the document to retrieve.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a fairly clear role: search finds relevant memories, list shows recent ones, get retrieves by ID, and save creates new content. Some minor overlap exists between search and list for locating memories, but the descriptions make the distinction workable.

Naming Consistency3/5

Most tools follow a verb_noun pattern (save_memory, list_memories, get_document), but search_memwyre breaks the pattern by using the product name instead of a noun like 'memories'. There is also mild inconsistency between 'memory' and 'document' as the noun for the same underlying resource.

Tool Count5/5

Four tools is a well-scoped size for a personal knowledge vault server. Each tool covers a distinct core operation—save, search, list, and get—without unnecessary bloat.

Completeness3/5

The server covers create and read workflows well, including semantic search, but it lacks update and delete operations for memories or documents. This is a noticeable gap in lifecycle coverage, though simple note-taking use cases can still succeed.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources