First of all, thank you all!
We’ve reviewed every topic and comment in the community, and your feedback is shaping the roadmap. Below is an honest update on where we are and where we’re heading. Some things are close to being done, others will take some time to figure out.
Making the connection reliable comes first
The connection and login problems that some of you ran into (ChatGPT/SSO drops, 403s, sessions that work in one chat but not the next) are the thing we most want to improve. We are reworking authentication to fix this properly. It also sets up the token work below.
More write access
You have been clear that read-only only gets you halfway. We are starting to open project write actions: schedule time entries, project equipment and scheduled crew. We are doing this carefully, so we respect the validation and logic behind these objects instead of exposing raw writes.
Tokens, scopes and trust
On the roadmap: multiple named API tokens (with creation date, individual deletion and traceability in the logs), scoped tokens, and an MCP connection tied to your own user. This way write access can be given safely and transparently.
We hear you, but not yet
Some of the biggest things you asked for are the full flow from a customer email to a project, quote and invoice, and generating documents. We get why those matter. For now we are building the project creation part. Full quote and invoice generation, and document generation, are still under consideration and not something we can commit to yet. The same goes for equipment availability requests.
Housekeeping
We are adding a “Developer email” field so we can actually reach you with updates. We are also expanding the endpoint descriptions in the API docs, which is clearer for you and gives better context to MCP/AI tools.
Please do keep your feedback coming - we need it to make the MCP better. And we will, of course, keep you updated as we roll out the improvements mentioned above and other changes.