PAMPA – Protocol for Augmented Memory of Project Artifacts (MCP compatible)
PAMPA – Protocol for Augmented Memory of Project Artifacts (MCP compatible). The pampa mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.
Give your AI agents an always-updated, queryable memory of any codebase – with intelligent semantic search and automatic learning – in one npx command.
Everything the assistant can do here goes through one of these:
Cursor — Configure Cursor by creating or editing the mcp.json file in your configuration directory:search_code — The search_code tool exposed by this serverget_code_chunk — The get_code_chunk tool exposed by this serverindex_project — The index_project tool exposed by this serverupdate_project — Update project index after code changes (recommended workflow tool)get_project_stats — The get_project_stats tool exposed by this serveranalyze_code — The analyze_code tool exposed by this serverfind_similar_functions — The find_similar_functions tool exposed by this serverpampa on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 3 environment variables: PAMPA_ENCRYPTION_KEY, OPENAI_API_KEY, COHERE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pampa's toolset — Cursor, search_code, get_code_chunk and 5 more — is a fair guide to whether it matches your workflow. It is maintained by tecnomanu; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Cursor | Configure Cursor by creating or editing the mcp.json file in your configuration directory: |
| search_code | The search_code tool exposed by this server. |
| get_code_chunk | The get_code_chunk tool exposed by this server. |
| index_project | The index_project tool exposed by this server. |
| update_project | Update project index after code changes (recommended workflow tool). |
| get_project_stats | The get_project_stats tool exposed by this server. |
| analyze_code | The analyze_code tool exposed by this server. |
| find_similar_functions | The find_similar_functions tool exposed by this server. |
{
"mcpServers": {
"pampa": {
"command": "npx",
"args": ["-y", "pampa"],
"env": {
"PAMPA_ENCRYPTION_KEY": "your-value",
"OPENAI_API_KEY": "your-value",
"COHERE_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PAMPA_ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| COHERE_API_KEY | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.