DearTech-OS for Claude
DearTech-OS connects to Claude Desktop and Claude Code through the Model Context Protocol (MCP). Once configured, Claude can search your company knowledge graph, traverse typed relationships, and ground its answers in source-attributed company context, without copying files into a project or re-explaining your business.
Last updated:
About Claude
What Claude is
Claude is Anthropic's AI assistant, available as Claude Desktop (Mac, Windows, Linux), Claude Code (terminal-based coding agent), and via web at claude.ai. Claude Desktop and Claude Code support the Model Context Protocol natively, making them first-class clients for DearTech-OS.
MCP support
Native MCP support in Claude Desktop and Claude Code. DearTech-OS is a first-class integration target for both clients.
Setup
Connect DearTech-OS to Claude
Configuration takes a few minutes. The exact paths depend on your client version, but the shape of the setup is consistent.
Locate your Claude config file
On macOS, Claude Desktop reads from ~/Library/Application Support/Claude/claude_desktop_config.json. Claude Code reads from .mcp.json in your repo or the user-level Claude config.
Add DearTech-OS as an MCP server
Add an entry under mcpServers pointing to mcp.deartech.co. Configure authentication using the credentials from your DearTech-OS deployment.
Restart Claude
Restart Claude Desktop for the new MCP server to be picked up. Claude Code reloads MCP config on session start.
Verify the connection
In a Claude conversation, ask 'what tools do you have access to?' or 'show me what DearTech-OS exposes.' You should see the graph search, read, query, and ingest tools listed.
Use cases
What you can do with DearTech-OS in Claude
Founder asks the company brain
From any Claude conversation, ask 'show me everything we know about ICP X' and Claude traverses the graph, pulling related concepts, customer evidence, and positioning with sources.
Source-grounded board prep
Claude drafts board updates citing the company graph: every claim links back to a node with status and confidence so the founder can verify before sending.
Onboarding without tribal knowledge
New hires query the graph through Claude in plain English. They get the same context the founder has, without months of side-conversations.
GTM context across surfaces
ICP, objections, positioning, and customer evidence are queryable in every Claude session, not stuck in one project's attached files.
FAQ
Common questions
Does this work with Claude Pro, Team, or Enterprise?
MCP support in Claude Desktop and Claude Code works across plan tiers. Specific role-based access controls (viewer, maintainer, admin) on the DearTech-OS side are independent of the Claude plan.
Do my teammates each need their own DearTech-OS access?
Yes. DearTech-OS uses SSO with role-based access. Each teammate signs in to DearTech-OS with their own role (viewer, maintainer, or admin) and Claude queries the graph with that teammate's permissions.
Can Claude write to the graph, or only read?
Both, controlled by role. Viewers can read and search. Maintainers can ingest new content. Admins can heal, crystallize, and audit. Claude inherits the role of the signed-in user.
Does Claude work without DearTech-OS?
Of course. Claude works fine without it. DearTech-OS adds shared, source-grounded company context to every Claude conversation. Without it, you are limited to per-conversation context, attached files, and Claude Projects.
Other integrations
Connect DearTech-OS to your other AI tools
DearTech-OS is AI-tool-agnostic. The same knowledge graph serves whichever MCP-compatible client your team uses.
Want DearTech-OS in your Claude sessions?
In a 30-minute call, we'll map where your company knowledge is scattered today and identify the first DearTech-OS layer worth building.