Tools from your own data
Every object gets tools to list, get, create, update and read history. A new field is available to the agent at once.
MCP server · AI agents
JaKun speaks the Model Context Protocol. Connect Claude, Cursor or any other MCP client, and the agent can find customers, create leads and log calls — only with the permissions you give it.
Every object gets tools to list, get, create, update and read history. A new field is available to the agent at once.
Writes run as a dry run by default: the agent sees what would happen, and nothing changes until it asks for it.
The agent uses an integration key with the roles you pick. It sees and changes no more than a user with the same roles.
Every call is recorded with key and time.
A message from the agent lands in the outbox. Sending to customers is switched on by the owner, with approved templates.
The construction pack adds e.g. find contact, upsert lead, log activity, callback queue and time tracking.
claude mcp add --transport http jakun https://jakun.dk/api/v1/mcp \
--header "Authorization: Bearer $JAKUN_TOKEN"
The Model Context Protocol is an open standard AI assistants use to call tools in other systems. JaKun's MCP server makes your CRM one of those tools.
Any client that supports remote MCP over HTTP with a header, e.g. Claude Code and Cursor.
Only what the key's roles allow. Writes are dry runs by default, and messages go to the outbox.