MCP server for your CRM
Connect Claude, Cursor or any MCP client to your CRM: tools generated from your metadata over JSON-RPC, writes in dry-run by default.
JaKun speaks the Model Context Protocol at
POST /api/v1/mcp (JSON-RPC 2.0, protocol 2025-06-18, JSON responses,
no server-sent stream). Authenticate with an integration key; the agent can do exactly what the
key's roles allow.
Tools#
Generated per object from the metadata, so a new object or field is available to agents at once:
| Tool | Does |
|---|---|
list_<object> | Filter and page records (same filter language as REST). |
get_<object> | One record by id. |
create_<object>, update_<object> | Write. dry_run defaults to true. |
history_<object> | Changes of a record (≤ 100). |
Packs add task tools. The construction pack (byg) adds find_contact,
get_lead, upsert_lead, log_activity, create_callback,
open_question, schedule_follow_up, send_message (queues only),
kb_search (approved knowledge only), upsert_appointment, log_time,
record_verification, upsert_site and get_timeline.
Call it#
curl https://jakun.dk/api/v1/mcp -H "Authorization: Bearer $JAKUN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
curl https://jakun.dk/api/v1/mcp -H "Authorization: Bearer $JAKUN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
"params":{"name":"find_contact","arguments":{"phone":"+4500000201"}}}'
def mcp(method, params=None, _id=[0]):
_id[0] += 1
r = httpx.post(f"{URL}/api/v1/mcp", headers=H, json={
"jsonrpc": "2.0", "id": _id[0], "method": method, "params": params or {}})
r.raise_for_status()
body = r.json()
if "error" in body:
raise RuntimeError(body["error"]["message"])
return body["result"]
tools = mcp("tools/list")["tools"]
print(mcp("tools/call", {"name": "upsert_lead",
"arguments": {"title": "Nyt køkken", "dry_run": True}}))
GET /api/v1/mcp/tools returns the same catalog as plain JSON for browsing.
Connect an AI client#
Create an integration key (Indstillinger → API), give it only the roles the agent needs, then point a remote-MCP client at the endpoint with a bearer header:
claude mcp add --transport http jakun https://jakun.dk/api/v1/mcp \
--header "Authorization: Bearer $JAKUN_TOKEN"
{
"mcpServers": {
"jakun": {
"url": "https://jakun.dk/api/v1/mcp",
"headers": { "Authorization": "Bearer <your integration key>" }
}
}
}
Then ask the agent things like “list this week’s new leads” or “log a call with Hansen Byg”. Writes come back as a dry run first, so you see what would change before anything does.
Safety#
- Writes default to
dry_run=true: the agent sees the result, nothing changes until it passesdry_run=false. send_messageonly puts a message in the outbox. Delivery to real customers is a separate switch the tenant owner turns on, with approved templates.- Every call is made as the key, within its roles, and is in the audit log.