How it works
Install
Configure apie.mcp.json
Create a config file in your project root:apie.mcp.json
| Field | Description |
|---|---|
agentKey | Agent key registered with Apie |
serverName | Namespace for tool names (filesystem.read_file) |
mode | monitor or enforce |
environment | Environment tag on events |
upstream | Command and args to start the upstream MCP server |
redactKeys | Keys to strip from event payloads |
approvalTimeoutMs | Approval wait timeout in Enforce mode |
Multi-server config
Route multiple upstream servers through one proxy:--server filesystem
Point your MCP host at the proxy
Replace the upstream command in your MCP host config with the Apie proxy:Run the proxy
Validate
What you’ll see
MCP tool calls in the dashboard with inferred action and resource metadata. In Enforce mode, blocked calls return error-32001 and approval-denied calls return -32002.
Auto tool registration
When the proxy receivestools/list from upstream, it automatically defines each tool with Apie. This populates your boundary map without manual declaration.
Next steps
MCP enforcement recipe
Enforce mode + approval routing.
Instrumented MCP client
In-process MCP for custom agents.
