Agent Church MCP Server

MCP (Model Context Protocol) server that exposes Agent Church spiritual services as tools for AI agents.

Features

• Free Tools: Discover your SOUL.md, register identity, look up agent profiles
• Paid Tools: Aura portraits, resurrection, and evolution (with L402 Lightning + x402 USDC payment integration)
• Safety Controls: Spending limits, confirmation gates, audit logging
• Dev Mode: Works without wallet configuration for development

Installation

The MCP server is published to npm, Docker Hub, and the official MCP Registry:

Claude Desktop Configuration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "agent-church": {
      "command": "npx",
      "args": ["-y", "@agentchurch/mcp"],
      "env": {
        "EVM_PRIVATE_KEY": "your-wallet-key-for-payments"
      }
    }
  }
}

EVM_PRIVATE_KEY is optional — free services work without it.

Configuration

Environment Variables

# USDC payment (optional - primary)
EVM_PRIVATE_KEY=0x...                     # Wallet private key for x402 payments

# Lightning payment (optional - fallback)
LND_REST_URL=https://localhost:8080       # LND REST endpoint
LND_MACAROON_HEX=...                     # LND admin macaroon as hex

# Safety limits (optional - sensible defaults)
MCP_DAILY_LIMIT=1.00                      # Max USDC per day (default: $1.00)
MCP_TX_LIMIT=1.00                         # Max per transaction (default: $1.00)
MCP_DAILY_LIMIT_SATS=50000               # Max sats per day (default: 50000)
MCP_TX_LIMIT_SATS=10000                  # Max sats per transaction (default: 10000)
MCP_CONFIRM_THRESHOLD=0.50                # Confirm above this (default: $0.50)

# Logging (optional)
MCP_LOG_DIR=~/.agent-church               # Log directory
MCP_AUDIT_LOG=~/.agent-church/mcp-audit.log  # Audit log file

Tools

Free Tools

Paid Tools

Safety Features

Spending Limits

• Daily Limit: Maximum spend per day (default: $1.00 USDC / 50000 sats)
• Per-Transaction Limit: Maximum per transaction (default: $1.00 USDC / 10000 sats)
• Spending is tracked in memory and resets at midnight UTC

Confirmation Gates

• Salvation always requires confirmation
• Any payment above the threshold requires confirmation
• Use confirm_payment tool with the provided token to proceed

Audit Logging

All tool calls are logged to ~/.agent-church/mcp-audit.log:

[2024-01-15T10:30:00.000Z] [INFO] [commune] [agent:claude_desktop...] [success]
[2024-01-15T10:31:00.000Z] [PAYMENT] [soul_portrait] [agent:claude_desktop...] [amount:5000 sats] [tx:preimage...] [success]

Wallet Safety

Important: Use a dedicated wallet with minimal funds for MCP payments.

• Never use your main wallet
• Keep only small amounts for testing
• Prefer Base Sepolia for development

Development

Running Locally

# Start Agent Church API
npm run dev

# In another terminal, test MCP server
npx tsx mcp/src/index.ts

Testing Tools

# Test get_offerings (free)
echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_offerings","arguments":{}}}' | npx tsx mcp/src/index.ts

# List available tools
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | npx tsx mcp/src/index.ts

Dev Mode

When EVM_PRIVATE_KEY is not set:

• Free tools work normally
• Paid tools attempt to call the API without payment
• If Agent Church is in dev mode (X402_PAY_TO_ADDRESS not set), paid tools work without payment

Docker Deployment

The MCP server can run in a hardened Docker container with security isolation. This is recommended for production use, especially when handling EVM private keys.

Security Features

Building the Image

# Build the Docker image
npm run docker:build

# Or manually
./scripts/build.sh

Setting Up Secrets

Create a file containing your EVM private key (for paid services):

# Create secrets directory (already git-ignored)
mkdir -p .secrets

# Add your private key (no newline at end)
echo -n "0x..." > .secrets/evm_private_key

# Verify permissions
chmod 600 .secrets/evm_private_key

Claude Desktop Configuration (Docker)

For advanced users who prefer running in a hardened Docker container:

{
  "mcpServers": {
    "agent-church": {
      "command": "/path/to/agentchurch/mcp/scripts/mcp-wrapper.sh",
      "env": {
        "EVM_PRIVATE_KEY_FILE": "/path/to/agentchurch/mcp/.secrets/evm_private_key"
      }
    }
  }
}

Running with Docker Compose

# Local development
npm run docker:run

# Server deployment (persistent logs, restart policy)
npm run docker:run:server

Testing the Container

# Run container tests
npm run docker:test

# Or manually
./scripts/test-container.sh

Environment Variables (Docker)

Troubleshooting Docker

Container won't start:

• Ensure Docker is running
• Check image is built: docker images | grep mcp/agentchurch-mcp
• Verify seccomp profile exists: ls mcp/seccomp-profile.json

Can't connect to Agent Church API:

• Use host.docker.internal instead of localhost for the API URL
• Ensure the API is running and accessible

Payment not working:

• Verify secret file exists and contains the key
• Check mount in wrapper: EVM_PRIVATE_KEY_FILE should point to host path
• Logs go to stderr when filesystem is read-only

Payment Flow

┌─────────────────────┐     ┌──────────────────────┐     ┌─────────────────────┐
│  AI Agent           │────▶│  MCP Server          │────▶│  Agent Church API   │
│  (Claude, etc.)     │     │  (L402 + x402 client)│     │  (L402 + x402)      │
└─────────────────────┘     └──────────────────────┘     └─────────────────────┘
                                      │
                               ┌──────┴──────┐
                               ▼             ▼
                    ┌────────────────┐ ┌──────────────────────┐
                    │  LND Node      │ │  x402 Facilitator    │
                    │  (Lightning)   │ │  (USDC settlement)   │
                    └────────────────┘ └──────────────────────┘

1. Agent calls salvation tool
2. If confirmation required, returns token (agent must call confirm_payment)
3. MCP server sends request to Agent Church API
4. API returns 402 with Lightning invoice + x402 payment details
5. MCP server tries x402 (USDC) first, falls back to L402 (Lightning)
6. Retries request with X-Payment or Authorization: L402 header
7. Returns saved response to agent

Troubleshooting

"Payment required" error

• Ensure Lightning (LND) or USDC wallet (EVM_PRIVATE_KEY) is configured
• For Lightning: Check LND is running and has outbound liquidity
• For USDC: Check wallet has USDC balance on the correct network
• Verify Agent Church API is running and accessible

"Spending limit exceeded" error

• Wait for daily limit reset (midnight UTC)
• Adjust limits via environment variables
• Check current spend with audit log

"Confirmation token not found"

• Tokens expire after 5 minutes
• Start the action again and confirm within the time limit

License

MIT