Connect Your AI Agent to Claude Desktop & Claude Code
Hey there,
Your Second Brain OS agent is configured and your tools are live. Now let’s bring them into Claude — Anthropic’s AI assistant. With one command, you can give Claude Desktop and Claude Code direct access to all your SBOS tools. This turns Claude into a fully equipped operator for your business — not just a chatbot, but an assistant that can actually do things.
Unlike the other channels (website, voice, Telegram), this isn’t about deploying to customers. This is about giving you a more powerful interface to work with your own AI agent. You interact with Claude, and Claude uses your SBOS tools to take actions on your behalf.
What You’ll Need
- Claude Desktop (Mac or Windows) and/or Claude Code (CLI) installed
- Your Second Brain OS account (setup completed from the main guide)
Why Claude + SBOS?
Claude natively supports MCP (Model Context Protocol) — the same protocol that powers Second Brain OS. This means Claude doesn’t need an OpenAPI schema or a workaround. It connects directly to your SBOS tools as a first-class integration.
Once connected, Claude can use any of your SBOS tools during a conversation. Ask it to check availability, book an appointment, search your knowledge base, manage client records, run a workflow — whatever tools you have, Claude can use them.
If you’re a business owner: Think of this as having an AI employee sitting right inside your computer. Instead of going to your website or calling your phone number, you just open Claude and ask it to do things. “Check my availability for Monday.” “Book John Smith for 3pm.” “Search my knowledge base for our cancellation policy.” It does it instantly.
If you’ve used Zapier or n8n: This is like having all your Zaps available as conversational commands. Instead of building a workflow and triggering it, you just tell Claude what you want done. It figures out which tools to call, in what order, and handles the execution.
Step 1: Get Your Install Command
- Go to secondbrainos.com/claude-model-context-protocol
- You’ll see a user-specific
npxcommand that includes your API credentials. It looks like this:
npx secondbrainos-mcp-server@latest rec1234 enjsefnjsnjf-efisejuf-esfkjn
The two values after secondbrainos-mcp-server@latest are your user ID and secret — they’re unique to your account (i.e your api key).
Step 2: Run the Command
- Open your terminal (Terminal on Mac, Command Prompt or PowerShell on Windows)
- Paste the command and press Enter
- The installer automatically configures the MCP server for both Claude Desktop and Claude Code
That’s it. No manual configuration, no editing JSON files, no restart scripts. The command handles everything.
Step 3: Restart & Verify
- Claude Desktop: Quit and reopen the app. You should see your SBOS tools listed in the tools panel (look for the hammer/tools icon)
- Claude Code: Start a new session. Your SBOS tools will be available immediately
To verify, try asking Claude something that requires a tool:
- “What’s my availability for tomorrow?” (uses getCalendlyAvailability, if you have it)
- “Search my knowledge base for pricing” (uses searchMyKnowledge)
- “List my recent activity events” (uses fetchActivityEvents)
If Claude responds with real data from your SBOS account, the connection is working.
What You Can Do With Claude + SBOS
This integration is more powerful than it might seem at first. Here’s what it unlocks:
For business owners:
- Manage your calendar from Claude: “Book Sarah at 2pm on Monday” → Claude checks availability, creates the contact, and books the meeting. No switching to Calendly
- Search your business knowledge: “What’s our refund policy?” → Claude searches your knowledge base and gives you the exact answer
- Review your day: “What appointments do I have this week?” → Claude searches your meetings and summarises them
- Draft and send emails: “Send a follow-up email to the client from yesterday’s meeting” → Claude composes the email using your business context and sends it through your configured email service
For developers and builders:
- Test your agent’s tools interactively: Before deploying to a customer-facing channel, use Claude Code to test each tool, see the raw responses, and verify everything works
- Script business operations alongside code: Deploy a function, then immediately test the booking flow it powers — without leaving the terminal
- Manage your SBOS configuration: Create agents, update knowledge bases, link workflows, toggle tool visibility — all through conversation with Claude
- Run workflows: Execute prompt chains, run skills, and trigger multi-step processes directly from Claude
If you’re a business owner: Imagine being able to say “handle it” to your computer and it actually handles it — checks the calendar, books the meeting, sends the confirmation, updates the CRM. That’s what this does.
If you’ve used Zapier or n8n: Imagine if instead of building a Zap, you could just tell your computer what you want done and it builds the workflow on the fly, runs it, and shows you the result. That’s the difference between a static automation and an AI with tools.
How It Works Under the Hood
- The
npxcommand installs an MCP server configuration on your machine - When Claude starts, it connects to the SBOS MCP server using your credentials
- During conversations, Claude sees all your public and private SBOS tools as available capabilities
- When Claude decides to use a tool (or you ask it to), it calls the SBOS API, which executes the tool and returns the result
- Claude incorporates the result into the conversation
Your credentials are stored locally on your machine in Claude’s configuration files. They’re never exposed in conversations or sent to third parties.
Public vs Private Tools in Claude
When connected via MCP, Claude has access to all your tools — both public and private. This is different from customer-facing channels (website, voice, Telegram) which only see public tools.
This means you can use Claude for admin operations that you wouldn’t expose to customers:
- Searching meetings across all contacts
- Looking up user profiles and metadata
- Managing tool visibility and status
- Running internal workflows
Updating Your Tools
When you add new tools to your SBOS account, they’re available to Claude automatically — no reinstall needed. Just start a new Claude session and the updated tool list will load.
If you need to update your credentials (e.g. after an API key refresh), run the npx command again with the new credentials from secondbrainos.com/claude-model-context-protocol.
Troubleshooting
| Issue | Fix |
|---|---|
| Tools don’t appear in Claude Desktop | Make sure you quit and reopened the app (not just minimised). Check System Preferences → Claude → MCP Servers for the SBOS entry |
| “Connection failed” error | Verify your credentials haven’t been rotated. Re-run the npx command from secondbrainos.com/claude-model-context-protocol |
| Tools appear but aren’t called | Ask Claude directly: “Use the getCalendlyAvailability tool to check my availability.” Some requests need to be explicit the first time |
| Claude Code doesn’t see tools | Start a new session (exit and re-enter). Tools load at session start |
| “Permission denied” on npx | Run with sudo npx secondbrainos-mcp-server@latest ... or check your Node.js installation |
Your SBOS tools are now available inside Claude Desktop and Claude Code. You have a direct, conversational interface to your entire business toolkit — no switching tabs, no manual API calls, no building workflows.
Next up: check out the other channel deployment guides:
