MCP
Plan your events from the assistant you already use.
What your assistant can do.
01
Create the event
Describe it and the assistant creates it: name, dates, how it runs, location or platform, starter tasks and ticket types. It lands as a draft, every time.
01
Create the event
Describe it and the assistant creates it: name, dates, how it runs, location or platform, starter tasks and ticket types. It lands as a draft, every time.
02
Build the task list
Ask for a plan and it writes the tasks, each with a due date, a cost estimate and an owner. You can reassign any of them from the same chat.
02
Build the task list
Ask for a plan and it writes the tasks, each with a due date, a cost estimate and an owner. You can reassign any of them from the same chat.
03
Source venues and suppliers
It searches the live web for real venues, scores them for fit and saves the shortlist to the event's Sourcing tab. It never invents a name, a capacity or a price.
03
Source venues and suppliers
It searches the live web for real venues, scores them for fit and saves the shortlist to the event's Sourcing tab. It never invents a name, a capacity or a price.
04
Invite and message guests
Bulk invitations, reminders to the people who have not replied, and check-in on the door. Anything that sends an email asks you first.
04
Invite and message guests
Bulk invitations, reminders to the people who have not replied, and check-in on the door. Anything that sends an email asks you first.
05
Read the numbers
Guests, tickets sold, revenue, budget against plan, open tasks and a health score, without opening the dashboard.
05
Read the numbers
Guests, tickets sold, revenue, budget against plan, open tasks and a health score, without opening the dashboard.
06
Publish when you are ready
Publishing is its own deliberate step, and so is cancelling. Both wait for you to say yes before anything happens.
06
Publish when you are ready
Publishing is its own deliberate step, and so is cancelling. Both wait for you to say yes before anything happens.
How it works.
01
Create a connection
In Mingloft, open Settings and create a connection. You get a URL and an access key. The key is shown once, so copy it there and then.
01
Create a connection
In Mingloft, open Settings and create a connection. You get a URL and an access key. The key is shown once, so copy it there and then.
02
Paste it into your assistant
Claude.ai takes the keyed URL on its own. Claude Code, Cursor, Windsurf and your own code take the URL and the key as a header.
02
Paste it into your assistant
Claude.ai takes the keyed URL on its own. Claude Code, Cursor, Windsurf and your own code take the URL and the key as a header.
03
Your assistant reads the tools
It asks Mingloft what it can do and gets the 17 tools back. Anything your plan does not cover comes back marked as locked, with the reason.
03
Your assistant reads the tools
It asks Mingloft what it can do and gets the 17 tools back. Anything your plan does not cover comes back marked as locked, with the reason.
04
Ask in plain language
Say what you want doing. The assistant picks the tool, Mingloft checks the request against your plan, and the work happens in your workspace.
04
Ask in plain language
Say what you want doing. The assistant picks the tool, Mingloft checks the request against your plan, and the work happens in your workspace.
05
Open what it changed
Every write returns a link to the record it touched. That link is the only one the assistant is allowed to give you, so it cannot send you somewhere that does not exist.
05
Open what it changed
Every write returns a link to the record it touched. That link is the only one the assistant is allowed to give you, so it cannot send you somewhere that does not exist.
Common questions
Connecting Mingloft to your assistant
Which assistants can I use?
Any client that speaks MCP. Claude.ai, Claude Code, Cursor, Windsurf, ChatGPT and your own code through the API. Clients with a header field take the URL and key; clients without one take the keyed URL instead.
Does it work with events I already have?
Yes. The assistant starts by listing the events in your workspace, so it works on the ones already there as well as anything new it creates.
What is the assistant allowed to change?
Reading works on every plan. Creating events, tasks and ticket types needs Field or above. Publishing, cancelling and anything that emails guests needs Pipeline or above, and asks you to confirm before it runs.
Do I need a developer to set this up?
No. Create the connection in Settings and paste what it gives you into your assistant. Claude.ai needs nothing installed; other clients take a single command.
Can it email my guests?
Only on Pipeline and above, and only after you say yes. Invitations and reminders both warn you before they run. Cancelling an event emails everyone who accepted, which is why that one asks for explicit confirmation.
Where do I manage the connection?
In Settings. Name each connection, see when it was created, and revoke it whenever you want. Revoking cuts off any client holding that key straight away.
Is the access key safe in a URL?
Treat the keyed URL like a password, because that is what it is. Mingloft redacts it from every log that records request paths. If you think it has leaked, revoke the connection and create a new one.
What if I am on the wrong plan?
Nothing breaks. The tool comes back marked as locked, along with the plan it needs, so your assistant can tell you instead of failing quietly.
Which assistants can I use?
Any client that speaks MCP. Claude.ai, Claude Code, Cursor, Windsurf, ChatGPT and your own code through the API. Clients with a header field take the URL and key; clients without one take the keyed URL instead.
Does it work with events I already have?
Yes. The assistant starts by listing the events in your workspace, so it works on the ones already there as well as anything new it creates.
What is the assistant allowed to change?
Reading works on every plan. Creating events, tasks and ticket types needs Field or above. Publishing, cancelling and anything that emails guests needs Pipeline or above, and asks you to confirm before it runs.
Do I need a developer to set this up?
No. Create the connection in Settings and paste what it gives you into your assistant. Claude.ai needs nothing installed; other clients take a single command.
Can it email my guests?
Only on Pipeline and above, and only after you say yes. Invitations and reminders both warn you before they run. Cancelling an event emails everyone who accepted, which is why that one asks for explicit confirmation.
Where do I manage the connection?
In Settings. Name each connection, see when it was created, and revoke it whenever you want. Revoking cuts off any client holding that key straight away.
Is the access key safe in a URL?
Treat the keyed URL like a password, because that is what it is. Mingloft redacts it from every log that records request paths. If you think it has leaked, revoke the connection and create a new one.
What if I am on the wrong plan?
Nothing breaks. The tool comes back marked as locked, along with the plan it needs, so your assistant can tell you instead of failing quietly.
Mingloft, inside your AI assistant.
17
Tools your assistant can call, from creating the event to exporting the guest list
1
Minute to connect. Create a key in Settings, paste it into your assistant
0
Events published by accident. Everything the assistant creates starts as a draft