It can call you
Most assistants wait in a tab. This one picks up the phone.
Give it a number. Give it yours. It can ring you — chase the quote, tell you what’s overdue, walk the board while you’re driving. You can call it too. Phone here means calls, not SMS.
The call is not a voicemail toy. It works the same records the pages show. “What’s still open?” on the phone gets an answer from the database. “Mark that job done” changes the record. When the call ends, the note is on the job.
That is the unique bit. Chat and email are there. The call is why you are not glued to the screen.
Use ours, or bring yours
Thogits is an AI-native workspace. The database is the system of record. Agents are how you work that record without living in a grid all day.
You have two paths. Use the built-in assistant. Connect your own agent over MCP. Or both.
They are not the same thing. Know the difference.
The built-in assistant
Chat, email, and calls
Our assistant lives in the product. It can:
- Call you, and take your call
- Chat with you inside the workspace
- Send and receive email
- Read and update records
- Build pages on those records
Ask what is open. Create a ticket. Request a dashboard for unpaid invoices. The assistant works the same data the screens show.
It is not a chatbot that talks about your work while the real facts sit in another tool. If you say “mark that job done,” the record changes. If you say “give me a board by crew,” you get a real page.
That is why this is not a chat window with no memory. The assistant has the database.
Bring your own agent via MCP
See and edit records
If you already run an agent — Claude, Cursor, something you built — you can point it at the space over MCP.
External agents can see and edit records. They can query the catalog, create things, update fields, and keep your data in line with however you already work.
MCP cannot:
- Build pages
- Run automations
- Run the full built-in agent loop (chat, email, and phone as one assistant)
Use MCP when you want your own agent on the data. Use our assistant when you want pages, email, and calls in the product.
What that looks like in practice
Teams often start in chat: “set up clients, jobs, and a week view.” Crews keep a page open on the laptop and email the assistant from the floor. Some people connect an existing coding agent over MCP to bulk-edit records, then open a Thogits page to see the result.
Typical jobs for the built-in assistant:
- A call to you: Friday 9:00, ring me if Oak Clinic still hasn’t paid
- Intake: someone emails in, a record appears
- Follow-up: you ask it to call or email a person on a record
- Build: you ask for a new page or a change to an existing one
- Query: “what is overdue?” gets an answer from the database, not a guess
Typical jobs for MCP:
- Your agent reads tickets and updates status from a repo or a script
- You keep a local workflow and treat Thogits as the system of record
- You do not want to rebuild CRUD for yet another tool
Same records, either way
Pages, reminders, integrations, and the API all sit on the same typed records. The assistant is one interface. MCP is another. A shared space means the people you invite see the same data the agents just changed.
Pick the interface that matches the moment. Do not split the facts.
Try it
Put a phone number on the assistant and on your account. Ask it to call you. Then try chat and email on the same record. If you already have an agent, connect MCP and edit a record from there. Full Features, pricing, or sign up and talk to your data.