Cowpin Agent Memory MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COWPIN_API_URL | No | The base URL of the Cowpin API. Defaults to https://www.cowpin.com | https://www.cowpin.com |
| COWPIN_AGENT_API_KEY | Yes | Your Cowpin Agent API key, generated from the Cowpin dashboard or via agent authentication. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cowpin_save_memoryA | Save a webpage URL or raw text/markdown notes into the persistent Cowpin memory vault with automated text extraction, OpenGraph metadata parsing, and 1536-dimensional vector embeddings. |
| cowpin_search_memoryB | Perform semantic vector and full-text keyword search over the agent's persistent memory vault using Reciprocal Rank Fusion. Returns relevant past research and snippets. |
| cowpin_get_balanceA | Check the current micro-credit balance, available queries, and on-chain USDC deposit address for this agent wallet. |
| cowpin_get_memory_pageB | Retrieve the full archived text and metadata of a specific memory by its ID or URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: saving, searching, checking balance, and retrieving full memory pages. Even though search returns snippets and get_memory_page returns full text, they serve different functions and are unlikely to be confused.
All tools follow the consistent pattern cowpin_<verb>_<object> (save_memory, search_memory, get_balance, get_memory_page). The 'get' prefix is used consistently for retrieval operations, making the naming predictable and uniform.
With 4 tools, the server is well-scoped for its purpose as a memory vault. The count is neither too thin nor excessive, and each tool contributes to core workflows (save, search, retrieve, and billing awareness).
The server covers save, search, and full-text retrieval, which are the primary operations for a memory vault. However, it lacks update and delete capabilities, which could be relevant if users need to correct or remove stored memories, though this may be intentional.