🔒 Why You Need This: Enterprise-Grade AI Security Meets Autonomous Agents

Giving AI assistants like Claude, Cursor, and Windsurf access to your codebase and the web is a superpower. But passing sensitive enterprise data to remote LLMs is a massive security risk. Furthermore, hitting token limits quickly degrades LLM context windows and increases costs.

The Problem: You want the massive productivity boost of agentic workflows, but you cannot compromise on Data Loss Prevention (DLP), compliance, leak prevention, or token bloat.

The Solution: AgenticStore MCP Server solves the entire equation natively:

• 🛡️ The LLM Prompt Firewall: A secure local proxy that intercepts, scans, and sanitizes your prompts before they leave your machine. It flags leaked secrets, PII, and API keys, using local models (like Ollama) to sanitize data and generate strict audit traces for all AI usage.
• 🧰 The MCP Toolkit (74 Tools): A production-ready arsenal. Instantly arm your AI with code analyzers and CVE vulnerability scanners, project health checks, safe local data inspection, context pruners, token optimizers, persistent semantic memory, and self-hosted SearXNG web search.
• ✦ Relay: A local project delivery system for humans and AI agents. Plan a project, create Epics and tickets, route work through Codex or Claude, and keep decisions, Git evidence, validation, and handoffs on the board.

Zero subscriptions. Zero vendor lock-in. Configure your MCP tools manually or effortlessly through a beautiful local GUI.

🎥 Prompt Firewall Demo

Your browser does not support the video tag. Take a look at the Prompt Firewall Demo video here.
(If the video above doesn't load, click here to watch the demo)

🎥 Watch the GUI Demo in Action (MCP Tools)

Your browser does not support the video tag. Take a look at the AgenticStore MCP GUI Demo video here.
(If the video above doesn't load, click here to watch the demo)

🏗️ How It Works

🔥 Why Choose AgenticStore MCP?

• 🛡️ LLM Prompt Firewall: Intercept, sanitize, and perform prompt recording for all data leaving your system, ensuring robust AI security.
• 🔒 100% Privacy-First: Everything runs locally. Generate reliable audit traces for AI usage while your code and data never leave your machine unaudited.
• ✂️ LLM Token Optimization: Radically reduce your token burn with code structural compression (token_optimizer) and relevance-based context trimming (context_pruner).
• 💸 Truly Free: No accounts, no paywalls, no subscriptions.
• 🧠 Persistent Agent Memory: Let your AI remember facts and contexts across sessions seamlessly.
• ⚡ Plug & Play: Installs instantly via uvx or pip. MCP configuration supports both manual JSON and GUI workflows.

📋 Table of Contents

• 🛡️ LLM Prompt Firewall & Sanitization
• 🧰 What's Inside the Toolkit
• 🚀 Quick Start Guide (Fastest Way to Install)
  • V0: Python/uvx (Recommended)
  • V1: From GitHub Source
  • V2: MCP Hub Webapp (UI)
• ✦ Relay: JIRA for AI Agents
• 🔌 Connect to Your AI Client
• 🗂 Tool Directory — All 74 Tools
• 💻 Claude Code CLI Integration
• 🔎 Enabling Web Search
• 🎛 Overriding Configs & Advanced Usage

🛡️ LLM Prompt Firewall & Sanitization

The Prompt Firewall gives you complete control over what natural language data and code leaves your computer when using cloud-based AI coding assistants, delivering enterprise-grade AI security.

Key Features:

• Proxy Interception: Set up a local proxy to monitor all LLM traffic.
• Audit Traces for AI Usage: Automatically generate prompt recording logs. Get clear warnings at each prompt level showing exactly what was changed or redacted.
• 1-Click UI Setup: Install certificate -> start proxy. The magic starts immediately. (Note: Firewall setup is only made available on the UI to ensure smooth installation and operation).
• Local LLM Integration (Optional): Connect your local Ollama instance. Download open-source models to run completely local, pre-flight prompt sanitization, scanning your code to make it better and safer before sending it to a remote API.
• Rule-Based Sanitization: Easily define regex or grammar rules to block PII, AWS keys, database strings, or proprietary logic.

To enable the firewall and begin collecting audit traces for AI usage, start the GUI Webapp and navigate to the Firewall tab to install the certificate and start the proxy. For deeper technical architecture, read the officially provided AgenticStore Prompt Firewall Documentation or visit the main site at agenticstore.dev.

GPT / OpenAI clients and custom redaction

MCP Hub → Clients now includes GPT / OpenAI Codex, with automatic TOML configuration and selected-tool support. The Codex CLI must be installed to apply the configuration. The Firewall dashboard also supports OpenAI SDK applications alongside Claude Code. Connect GPT / OpenAI SDK to route Chat Completions and Responses requests through http://127.0.0.1:8766/openai/v1. Settings now include Redaction Replacement for your own literal placeholder; blank restores the typed defaults. Prompt recordings store the sanitized prompt that is forwarded upstream by default. In the Firewall → Recordings tab, you can explicitly choose to retain the original pre-sanitization prompt locally when an investigation requires it. See the OpenAI setup and coverage guide.

🧰 What's Inside the Toolkit (74 MCP Tools)

Equip your AI client with these modules containing 74 specific MCP tools, categorized strategically for maximum productivity:

• 🛡️ Local Only: 62 tools with openWorldHint: false; they stay within local or configured closed environments.
• ☁️ Open World: 12 tools that can reach public web or remote-provider systems.
• 📝 Stateful: 21 tools that can write local state, execute a bounded action, or change an external system; explicit confirmation is required where applicable.
• 👓 Read Only: 53 tools marked retry-safe through MCP annotations.

🚀 Quick Start Guide (Fastest Way to Install)

Pick the setup that best fits your workflow. MCP supports both manual configuration and GUI-based management setup. Don't know which to pick? Start with V0.

pip install agentic-store-mcp --upgrade

agentic-store-mcp

agentic-store-mcp --version

pip install git+https://github.com/agenticstore/agentic-store-mcp.git

agentic-store-mcp

# Ensure it is installed via pip
pip install agentic-store-mcp --upgrade

# Launch the web UI  automatically bundled with the core package
agentic-store-webapp 

✦ Relay: JIRA for AI Agents

Relay is AgenticStore's local delivery system for projects shared by people and AI agents. It lives in the webapp and stores its board on your machine, so project context stays available across agent sessions.

Use Relay to create multiple boards, group work into Epics, assign each ticket to an isolated workspace, and run Codex or Claude handoffs in parallel. Each ticket can retain progress comments, validation results, Git evidence, decision context, blockers, and the session that worked on it.

Triage with the AI Task Planner

Open Relay → AI task planner and describe the outcome, success criteria, constraints, product surfaces, and quality requirements. Relay opens a local Codex or Claude planning session with a reusable planning harness. The planner inspects the selected board, asks follow-up questions, proposes an Epic with bounded child tickets, and waits for your explicit approval before it creates work in bulk.

The harness makes automated tests and documentation part of the plan whenever code or user-facing behavior changes. It also prompts for security, accessibility, migration, rollout, and rollback work when relevant. Planning sessions are recorded in Relay so the rationale remains with the project.

A practical workflow

1. Create a board for a product, release, or client initiative.
2. Use AI task planner to turn a goal into an approved Epic and testable tickets.
3. Assign tickets to local checkouts or fresh remote clones, then hand them to Codex or Claude.
4. Review work through recorded comments, validations, and Git evidence; drag tickets through delivery states as work progresses.

Relay does not send project data to a hosted planning service. It launches the local agent client you select, which uses its own configured model and privacy settings.

🔌 Connect to Your AI Client

Because AgenticStore MCP supports both manual configuration and management via the GUI, you can manually add the configuration snippet to your respective client's config file if you prefer. Remember to restart the client after saving! For an in-depth guide on linking AI agents properly, visit the Client Connection Documentation on agenticstore.dev.

Standard Copy-Paste Config

Basic Setup:

{
  "mcpServers": {
    "agentic-store-mcp": {
      "command": "agentic-store-mcp",
      "args": []
    }
  }
}

With Web Search (SearXNG) enabled:

{
  "mcpServers": {
    "agentic-store-mcp": {
      "command": "agentic-store-mcp",
      "args": [],
      "env": {
        "SEARXNG_URL": "http://localhost:8080"
      }
    }
  }
}

🗂 Tool Directory — All 74 Tools

💻 Claude Code CLI Integration

AgenticStore MCP is fully compatible with Claude Code explicitly for terminal workflows, allowing developers full access to the 74 command capacities directly interacting via the command line.

Safe CLI Execution Modes

Automatically install the application directly into your ~/.claude/settings.json seamlessly resolving connection bindings. The CLI handles both traditional operation and state-of-the-art intercepting proxy verification cleanly via a dynamic CLI command structure.

Default Mode: (For direct API calling — connects to normal Anthropic models purely without firewall tracking):

agentic-store-mcp --install-claude

• Explicitly registers to the user's ~/.claude/settings.json locally.
• Actively forces launchctl unsetenv cleanup dropping any stale ANTHROPIC_BASE_URL routing bindings to assure 100% stable connection directly to Anthropic standard APIs.
• Removes proxy-forcing traces dynamically from your target system environment ~/.zshrc/~/.bash_profile — new terminals always start completely clean.

Firewall Mode: (Pre-validates proxy stability mapping traffic efficiently directly into Prompt Recoding security boundaries protecting enterprise secrets):

agentic-store-mcp --install-claude --firewall-mode

• First natively verifies the AgenticStore firewall proxy is correctly listening across Port 8766 before touching configuration trees preventing deployment breakages completely.
• Formally injects launchctl setenv routing instructions properly writing nc-guarded shell profile blocks into Node.js TLS ANTHROPIC_BASE_URL interception directly into Claude.

(Note: --firewall-mode explicitly refuses to run unaccompanied. It requires --install-claude actively passed alongside it).

Manual Configuration

Run claude mcp add agentic-store-mcp "agentic-store-mcp".

🔎 Enabling Web Search

To give your agent internet access, agentic_web_search uses a private SearXNG instance.

If you'd like to use a remote API or host your own container, simply append its URL.

Pass the environment variable to your AI Client:

{
  "mcpServers": {
    "agentic-store-mcp": {
      "command": "agentic-store-mcp",
      "args": [],
      "env": {
        "SEARXNG_URL": "http://localhost:8080"
      }
    }
  }
}

🎛 Overriding Configs & Advanced Usage

Overriding configs is related to your MCP setup. MCP supports both manual and GUI setup, so you can filter exactly what tools get loaded via environment variables if integrating deeply without the web GUI.

# Debug: List what would be loaded and exit
agentic-store-mcp --list

Note: The LLM Prompt Firewall is exclusively configured via the UI. The firewall is only made available on the UI to ensure smooth setup, robust proxy interception, and seamless prompt recording out of the box.

Focused tool profiles

AgenticStore can run a focused subset of tools for a specific job. Use tool_orchestrator to recommend a profile, save it through tool_profile_manage, audit its safety boundaries with tool_profile_audit, then restart the MCP client with that profile:

agentic-store-mcp --profile private-code-review

Profiles always retain the three profile-control tools. A profile changes the tool list supplied at client connection time, so restarting the client is required after a profile is created or changed.

🛠️ Troubleshooting

Internet Disruption After Proxy Use When dealing with the LLM Prompt Firewall proxy, if the server is terminated abruptly, there could be an internet disruption on your machine due to residual system proxy settings.

If you lose internet connection after a crash, run this command in your terminal to restore your proxy to default:

networksetup -setsecurewebproxystate "Wi-Fi" off

🤝 Contributing & Community

Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you'd like to contribute code or improvements, please fork the repository and create a Pull Request.

⭐ If this toolkit saved you 10 hours of configuration, please give us a star to help others find it!

📜 License & Support

This project is licensed under the MIT License — free to use, modify, and distribute. See LICENSE for details.

Codex with ChatGPT login can route model requests through the TLS firewall using the GPT / Codex connection control. HTTP and outgoing JSON WebSocket prompts are supported; restart Codex and verify a new recording. See Codex proxy setup.

Firewall Audit Log now filters Blocked / errors and Sanitized entries and includes a Reveal original matched values toggle. New audit findings store original matches locally; originals are hidden from the default response and display. Older category-only entries cannot recover original values. Clear removes the saved audit details.

When you stop the dashboard with Ctrl+C, AgenticStore restores the macOS HTTP/HTTPS proxy settings saved before installation and then stops its listener. A separate watchdog restores routing after an unexpected server or proxy failure. See network proxy recovery for limitations.