hackerdogs/aws-bedrock-custom-model-mcp repository overview

⁠

⁠AWS Bedrock Custom Model MCP Server

MCP server wrapper for Bedrock Custom Model Import⁠ — import and manage custom fine-tuned models in Amazon Bedrock.

⁠What is Bedrock Custom Model Import?

Amazon Bedrock Custom Model Import allows you to bring your own fine-tuned models (such as those trained externally or via SageMaker) into Bedrock so they can be served through the same managed inference API as foundation models. This MCP server lets AI assistants create import jobs, track their status, list imported models, and manage the lifecycle of custom models within Bedrock. See awslabs/mcp⁠ for full documentation.

AWS credentials required — set AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_REGION.

Summary. MCP server wrapper for Bedrock Custom Model Import⁠ — create and manage import jobs to bring fine-tuned models into Amazon Bedrock's managed inference platform.

⁠Tools Reference

⁠Example Prompts

Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:

• "List all custom model import jobs in my Bedrock account and show their status."
• "Show me all successfully imported custom models available in Amazon Bedrock."
• "Start a new model import job for the fine-tuned model stored in my S3 bucket."
• "Check the status of my in-progress Bedrock model import job."
• "List my Bedrock custom models and show which ones are currently active and invokable."
• "Delete a completed custom model import job that is no longer needed."

⁠Deploy

⁠Docker Compose (recommended)

docker-compose up -d

⁠Docker Run (stdio mode)

docker run -i --rm \
  -e AWS_REGION \
  -e AWS_ACCESS_KEY_ID \
  -e AWS_SECRET_ACCESS_KEY \
  hackerdogs/aws-bedrock-custom-model-mcp:latest

⁠Docker Run (HTTP streamable mode)

docker run -d -p 8605:8605 \
  -e MCP_TRANSPORT=streamable-http \
  -e MCP_PORT=8605 \
  -e AWS_REGION \
  -e AWS_ACCESS_KEY_ID \
  -e AWS_SECRET_ACCESS_KEY \
  hackerdogs/aws-bedrock-custom-model-mcp:latest

⁠MCP Client Configuration

⁠Stdio mode (default)

Add to your Claude Desktop or Cursor MCP config:

{
  "mcpServers": {
    "aws-bedrock-custom-model-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AWS_REGION",
        "-e",
        "AWS_ACCESS_KEY_ID",
        "-e",
        "AWS_SECRET_ACCESS_KEY",
        "hackerdogs/aws-bedrock-custom-model-mcp:latest"
      ],
      "env": {
        "MCP_TRANSPORT": "stdio",
        "AWS_REGION": "",
        "AWS_ACCESS_KEY_ID": "",
        "AWS_SECRET_ACCESS_KEY": ""
      }
    }
  }
}

⁠HTTP mode (streamable-http)

First, start the server using Docker Compose or docker run with HTTP mode (see Deploy⁠ above), then point your MCP client at the running server:

{
  "mcpServers": {
    "aws-bedrock-custom-model-mcp": {
      "url": "http://localhost:8605/mcp"
    }
  }
}

⁠Environment Variables

⁠Installing in Hackerdogs

The fastest way to get started is through Hackerdogs⁠:

1. Log in to your Hackerdogs account.
2. Go to the Tools Catalog.
3. Search for the tool by name.
4. Expand the tool card and click Install — you're ready to go.

1. Vendor API key required? Add your key in the config environment variable field before clicking Install. Your key will be encrypted at rest.
2. Enable / Disable the tool anytime from the Enabled Tools page.
3. Need to update a key or parameter? Go to My Tools → toggle Show Decrypted Values → edit → Save.

⁠Build

docker build -t hackerdogs/aws-bedrock-custom-model-mcp:latest .

⁠Testing

⁠Automated tests

./test.sh

⁠Test directly with Docker

1. Start the server in HTTP mode:

docker run -d --rm --name aws-bedrock-custom-model-mcp-test -p 8605:8605 \
  -e MCP_TRANSPORT=streamable-http \
  -e AWS_REGION \
  -e AWS_ACCESS_KEY_ID \
  -e AWS_SECRET_ACCESS_KEY \
  hackerdogs/aws-bedrock-custom-model-mcp:latest

2. Initialize the MCP session:

SESSION_ID=$(curl -s -D - -X POST http://localhost:8605/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
  2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')

curl -s -X POST http://localhost:8605/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","method":"notifications/initialized"}'

3. List available tools:

curl -s -X POST http://localhost:8605/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

4. Clean up:

docker stop aws-bedrock-custom-model-mcp-test