MCP + AMAZON BEDROCK AGENTCORE

Your agent. With event context.

A separate, read-only MCP service adapts SmartDetector’s existing REST API. It does not expose administrator controls.

Available tools

list_events

List recent incident events in the API key organization.

events:read

get_event

Read one incident event and its recorded observations.

events:read

list_devices

List monitored devices in the API key organization.

devices:read

get_device

Read the status of one monitored device.

devices:read

explain_event

Return recorded event observations and any existing AI summary for explanation. Does not invoke a model or change state.

events:read

Run locally

  1. Start SmartDetector and create a read-only API key with events and devices scopes.
  2. Set a separate random MCP client token (at least 32 characters).
  3. Start the MCP container from the pinned submodule.
git submodule update --init --recursive
export SMARTDETECTOR_API_KEY='YOUR_READ_ONLY_KEY'
export SMARTDETECTOR_MCP_AUTH_TOKEN="$(openssl rand -hex 32)"
docker compose -f submodules/smartdetector-agentcore/docker-compose.yml up --build

The local MCP endpoint is http://localhost:8083/mcp. It requires Authorization: Bearer YOUR_MCP_CLIENT_TOKEN, not your REST API key. The container injects the REST key into upstream calls to SmartDetector at port 8082.

Connect your MCP client

{
  "mcpServers": {
    "smartdetector": {
      "url": "http://localhost:8083/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_CLIENT_TOKEN"
      }
    }
  }
}

Generic HTTP MCP configuration; use your client’s supported configuration format and secret storage. Do not commit real tokens.

Try a prompt

“List recent SmartDetector events. Read the latest event and explain the recorded observations. Separate detector measurements from AI interpretation; do not infer identity or intent.”

The review_recent_events MCP prompt is also available. explain_event returns recorded context; it does not invoke Bedrock or change alarm state.

Deploy in AgentCore

The separate ARM64 runtime container uses the same tool contract. Its CloudFormation template configures the runtime, scoped role, and Secrets Manager access. AWS IAM protects the runtime boundary; local Bearer authentication is not an AWS deployment substitute.

Runtime package & CloudFormation quickstart ↗

Marketplace publication and live AWS verification are separate from local testing. Never enable AgentCore authentication mode on a public local server.

REST API reference →