# Constructoo MCP Server

Standalone mock MCP server for validating Constructoo Copilot data access through an Agent Builder MCP node.

## Goal

Validate this chain before the production backend is ready:

```txt
ChatKit UI
-> Agent Builder workflow
-> MCP node
-> Constructoo MCP server
-> mock Constructoo data
```

## Mock Tools

Read-only tools exposed by this server:

- `count_customer_properties`
- `get_customer_properties`
- `get_project_status`
- `get_today_appointments`

## Run Locally

```sh
npm install
npm run dev
```

Local endpoint:

```txt
http://127.0.0.1:8788/api/mcp
```

Quick metadata check:

```sh
curl http://127.0.0.1:8788/api/mcp
```

Tool call example:

```sh
curl -X POST http://127.0.0.1:8788/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"count_customer_properties","arguments":{"customerName":"Charlie"}}}'
```

Expected result:

```json
{
  "customerName": "Charlie",
  "propertyCount": 2
}
```

## Deploy

Deploy this folder as its own Vercel project.

After deployment, use this URL in Agent Builder's MCP node:

```txt
https://YOUR_VERCEL_DOMAIN/api/mcp
```

## Agent Instruction Suggestion

```txt
When the user asks about Constructoo customers, properties, projects, appointments, or project status, use the Constructoo MCP tools. Do not guess app data.
```

## Notes

- This server intentionally uses mock in-memory data only.
- Do not add write/update tools until read-only MCP access is verified.
- Production should replace mock data with real backend calls or move this MCP endpoint into the backend.