Custom MCP Server

Bring your own MCP (Model Context Protocol) server to extend D.A.M.I with custom tools.

This feature lets you connect any tool that implements the MCP protocol — internal tools, custom APIs, or third-party services not yet in our catalog.

Prerequisites

An MCP-compatible server endpoint (HTTP)
The server must implement the MCP tool discovery protocol

Setup

1. Prepare Your MCP Server

Your server must expose these endpoints:

GET  /tools        → List available tools
POST /tools/call   → Execute a tool

2. Connect via D.A.M.I

curl -X POST https://api.dami.dev/api/v1/connectors/connect \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "template_id": "custom_mcp",
    "config": {
      "server_url": "https://your-mcp-server.example.com",
      "api_key": "optional-auth-key",
      "server_name": "My Custom Tools"
    }
  }'

3. Discover Tools

Once connected, D.A.M.I automatically discovers all tools exposed by your server:

curl https://api.dami.dev/api/v1/connectors/YOUR_CONNECTOR_ID/discover \
  -H "Authorization: Bearer YOUR_TOKEN"

MCP Server Specification

Your MCP server should return tools in this format:

{
  "tools": [
    {
      "name": "deploy_service",
      "description": "Deploy a microservice to production",
      "inputSchema": {
        "type": "object",
        "properties": {
          "service_name": { "type": "string" },
          "version": { "type": "string" }
        },
        "required": ["service_name", "version"]
      }
    }
  ]
}

Risk Classification

D.A.M.I automatically classifies your custom tools:

Pattern	Risk Level	Behavior
`get_`, `list_`, `search_*`	READ	Execute immediately
`create_`, `update_`	WRITE	Requires confirmation
`delete_`, `destroy_`	DESTRUCTIVE	Requires explicit approval

You can override risk levels in the connector configuration.

GitHub API Reference