Agent MCP Server

18 tools: agent memory, API drift detection, and HMAC-signed trust receipts

Local serverstdio

What is the Agent MCP server?

18 tools: agent memory, API drift detection, and HMAC-signed trust receipts. That is what the agent mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Service — Env Var
  • Memory — AGENT_MEMORY_API_KEY
  • Drift — AGENT_DRIFT_API_KEY
  • Receipts — TRUST_RECEIPT_API_KEY

What it needs from you

Configuration is passed through the environment: AGENT_MEMORY_API_KEY, AGENT_DRIFT_API_KEY, TRUST_RECEIPT_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

The server ships on npm as @lulzasaur9192/agent-infra-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Agent's toolset — Service, Memory, Drift and 1 more — is a fair guide to whether it matches your workflow. It is maintained by lulzasaur9192; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Agent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ServiceEnv Var
MemoryAGENT_MEMORY_API_KEY
DriftAGENT_DRIFT_API_KEY
ReceiptsTRUST_RECEIPT_API_KEY

How to install the Agent MCP server

### Claude Desktop / Cursor

```json
{
  "mcpServers": {
    "agent-infra": {
      "command": "npx",
      "args": ["-y", "@lulzasaur9192/agent-infra-mcp"],
      "env": {
        "AGENT_MEMORY_API_KEY": "your-key",
        "AGENT_DRIFT_API_KEY": "your-key",
        "TRUST_RECEIPT_API_KEY": "your-key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
AGENT_MEMORY_API_KEYCredential the server authenticates with.Yes
AGENT_DRIFT_API_KEYCredential the server authenticates with.Yes
TRUST_RECEIPT_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Agent to Service.
  • Use Agent to Memory.
  • Use Agent to Drift.

Frequently asked questions

It connects Agent to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Service, Memory, Drift, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agent directly.