You can bring an agent you already have. You can use ours. You can use both.
That sentence is the product. The rest is the split, because “agent” is a sloppy word and we should not be sloppy about what each door can do.
Two doors
MCP is how an external agent talks to Thogits. Claude, Cursor, anything that speaks MCP. It can see your records and edit your records. Query, create, update, delete. That is the surface.
The built-in assistant lives in Thogits. Chat in the product, email, phone calls. It can create and update records. It can also build pages. It can talk to people on channels MCP does not have.
MCP = records.
Our agent = records + pages + comms.
If you remember one line from this post, remember that one.
What MCP is for
You already have an agent in Claude, or in Cursor, or in some other client that can attach an MCP server.
You connect it to your Thogits space. The agent can then work the same database you see in the product. “What jobs are open.” “Add a client.” “Mark that invoice paid.” The record changes. The pages that sit on those records update because they are looking at the records, not at a copy.
This is useful when the agent is already in your loop. You are in a coding tool and you want the job list. You are in a chat tool you already pay for and you want it to stop being a dead-end conversation. You want one agent that already knows your other work to also know Thogits.
It is not a second Thogits. It is a records door.
Settings in the product is where you connect. The API exists for custom setups that are not MCP. Integrations are the other way around — pulling other systems in. MCP is specifically: your agent, our records.
What MCP is not
MCP does not build pages.
It will not compile a dashboard. It will not build the page for last week’s finished tickets. If you ask an external agent to “make me a page,” it can at best talk about a page. Page generation is inside Thogits.
MCP does not email your clients. It does not place a phone call. Those channels are the built-in assistant.
MCP does not run your reminders or your automations. Those live in the workspace. Automations are schedule-based: remind you, wake an assistant, run a script. They fire at a time. They are not “when a record changes.” An external agent can edit a record; it does not become the scheduler.
Keep the claims small and they stay true.
What the built-in assistant is for
The assistant is the one that lives here.
You chat with it in the product. You can give it an email address. On paid plans it can have a phone number and take calls. Chat, email, call — three ways in. It reads and writes records in all of them.
It can also build pages. “Make a dashboard of open jobs and unpaid invoices.” That is an assistant job, not an MCP job.
Voice or email in, records persist. Same as if you typed them. Web and iPhone stay in sync. No offline mode.
You invite coworkers to the space. They see the same records and pages. The people doing the work share the system. You are not buying a permission tree.
When you would use which
Use MCP when the agent is already elsewhere and you want it to see Thogits data.
Use the built-in assistant when you want a channel (chat, email, call), or when you want a new page, or when you want the thing that already knows this workspace.
Use both when that is the truth of how you work. External agent updates a job from Cursor. You open the page on your phone. Later you call the built-in assistant on the drive home and add a follow-up. One database.
Say you run a small shop. Cursor has MCP connected. You tell it to create next week’s jobs from a list. The records appear. You still ask the Thogits assistant for the dashboard those jobs sit on. MCP wrote records. The assistant wrote the page.
That shop might keep the work as tickets, the people as a CRM, and money as invoices — who owes what, not a payments product. The agent doors do not care which shape you started from. They care that the records are real.
A note on “agents” as a category
A lot of tools will say they have agents. Some of those agents write text. Some write code. Some click around a browser. Few of them are looking at your actual system of record.
Thogits starts from the records. Pages are screens on those records. The assistant acts on those records. MCP acts on those records. That is why bringing your own agent works: there is something solid to bring it to.
If you want the product in one page, read What is Thogits. If you want to see a whole small-business shape — clients, jobs, invoices, follow-ups, one dashboard — there is a walkthrough: Running a small business on Thogits. Pages themselves are unpacked in Pages the AI actually builds.
The same records can look like projects, a directory, todos, or docs. Personal and teams are scale, not a different product. Templates are a starting system you can then change.
Limits, said plainly
External agents get records. They do not get page compile. They do not get our phone line.
Automations do not trigger on field edits. They trigger on a schedule.
Invites are to the space, not to a permission role.
Sync is live on web and iOS.
Invoice records track who owes what. They are not a payments product.
Those limits are the same whether you came in through MCP or through chat.
Start
Connect the agent you already have, or open the one that is already in the workspace.
If you only need records from the outside, MCP is enough. If you need pages and a number people can call, use ours. If you need both, that is the design.
Pricing is per workspace. Try the records door and the assistant on the same data. The point of bringing your own agent is not a demo. It is that the database was real before the agent arrived.