Slate HQ Ltd
not read yet
Use
- For
- People who want personal and work context kept separate across the AI tools they use.
- Runs as
- Desktop app
- Used for
- Give Claude or Cursor saved personal preferences and decisions
- Share current task context with a Mac or terminal session
- Keep personal notes separate from work context in AI chats
Figure and bar: visits/mo, estimate · year: online since
- #1
xTilesMCP · sign-in
Organizes tasks, notes and projects into daily plans and reviews, with MCP connections that let Claude or ChatGPT reach them.
6kActiveFrom $12.42/user/mo - #2
DayzeMCP · open
Builds a linked record of your contacts, calendar and receipts that chat assistants can query and add to through MCP.
5.9kActiveFrom $120/yr2024 - #3
NexaLinkMCP · sign-in
Scans business cards, receipts and whiteboards into a searchable record, then drafts follow-up messages from what was captured.
2.3kActiveFrom $39 once - #4
TabflowsMCP · open
Shared team chat, task manager and patient-matching layer that links clinic EHR, messaging, lab and fax systems and triages incoming work.
991ActiveFrom $2,000/mo2024 - #5
PromptQL
Coordinates work across team members by connecting bots to shared data sources and maintaining context in documents, dashboards, and chats.
499ActiveFrom $40/user/mo - #6
Byterover
Stores and syncs project context across AI agents and team members with access control and source attribution.
137From $15/mo
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Slate HQ Ltd for?
Sign in to leave a noteWhat is Slate HQ Ltd?
Stores your private personal context and serves preferences and decisions to connected AI clients through an MCP address. It is listed in the Atlas under Productivity.
Who is Slate HQ Ltd for?
People who want personal and work context kept separate across the AI tools they use.
Do people use Slate HQ Ltd?
Little sign of use.
What are alternatives to Slate HQ Ltd?
In Productivity, by use: xTiles, Dayze, NexaLink, Tabflows, PromptQL, Byterover.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.