Skip to main content
Glama

Tom Osborne's Second Brain — MCP server

Talk to Tom Osborne's voice-cloned AI agent from inside Claude Desktop, Claude Code, Cursor, Cline, or any Model Context Protocol–compatible client.

Built on Tom's 100-question interview corpus, 15 years of operator memory, and 21,000+ curated marketing knowledge-base articles across 17 verticals (paid, content, SEO, sales, leadership, PR, ads, design, HR, finance, legal, local, marketing fundamentals, business strategy, creator, community, entrepreneurship).

What it does

Adds one tool to your MCP client:

ask_tom(question: string) → Tom's answer in his voice, with KB chunks retrieved

When called, it POSTs your question to https://tomosborne.me/api/cmo/chat along with your configured email, and returns Tom's reply. The same pipeline that powers tomosborne.me/cmo — same retrieval, same security gate, same voice.

Related MCP server: videoseek-mcp

Installation

1. Install via npm

npm install -g @tom-osborne/second-brain-mcp

(Or run via npx @tom-osborne/second-brain-mcp if you prefer not to install globally.)

2. Add to your MCP client config

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "second-brain": {
      "command": "npx",
      "args": ["-y", "@tom-osborne/second-brain-mcp"],
      "env": {
        "MCP_TOM_EMAIL": "you@yourcompany.com"
      }
    }
  }
}

Restart Claude Desktop. The ask_tom tool will appear in the MCP tools panel.

Claude Code

Add to your project's .mcp.json:

{
  "mcpServers": {
    "second-brain": {
      "command": "npx",
      "args": ["-y", "@tom-osborne/second-brain-mcp"],
      "env": {
        "MCP_TOM_EMAIL": "you@yourcompany.com"
      }
    }
  }
}

Or via the CLI:

claude mcp add second-brain -e MCP_TOM_EMAIL=you@yourcompany.com -- npx -y @tom-osborne/second-brain-mcp

Cursor / Cline / other MCP clients

Use the same shape — point at npx @tom-osborne/second-brain-mcp with MCP_TOM_EMAIL in env.

Usage

Once installed, in any MCP-aware chat:

Use ask_tom: how do I get to my first 100 customers as a DTC brand?

The tool returns Tom's answer in his voice, drawing on his interview corpus + the 21k-article KB.

Quotas

  • Free tier: 5 questions per day per email (rate-limited at the API)

  • Coffee unlock: +20 questions/day + faster replies + voice replies — buy at https://tomosborne.me/cmo

  • Loyalty: every 6 coffees = 24h/7d/30d VIP unlock (unlimited premium)

If you hit the cap, the tool returns a clear "go upgrade" message rather than failing silently.

Environment variables

Variable

Required

Default

Purpose

MCP_TOM_EMAIL

Yes

Your email — used for daily quota tracking. Must be a real email.

MCP_TOM_API_KEY

No

Optional API key for higher-tier access (gate is server-side; ignored if not configured)

TOM_API_BASE

No

https://tomosborne.me

Override the API base (only useful for dev/testing)

Privacy

  • Your questions are sent to tomosborne.me/api/cmo/chat over HTTPS

  • Email is stored against your daily quota counter; never shared, never sold

  • The Pages Function applies the same security filter set as the public /cmo chat (no wallet addresses, API keys, or PII in responses)

  • Source: tomosborne.me is open-source-ish in spirit — DM Tom if you want to peek under the hood

Local development

git clone https://github.com/DegenDoes/second-brain-mcp.git
cd second-brain-mcp
npm install
MCP_TOM_EMAIL=test@you.com npm run dev   # tsx in watch mode

Test it via the MCP Inspector:

npx @modelcontextprotocol/inspector npx -y @tom-osborne/second-brain-mcp

License

MIT. Use it however you like. If you build something cool with it, tell Tom.

Available Tools

1 tool
ask_tomA

Ask Tom Osborne's second brain a question about marketing, growth, paid ads, eCommerce, content, leadership, or how Tom can help you. Returns Tom's answer in his voice, drawing on his 100-question interview corpus, 15 years of operator memory, and 21,000+ curated marketing knowledge-base articles across 17 verticals (paid, content, SEO, sales, leadership, PR, ads, design, HR, finance, legal, local, marketing fundamentals, business strategy, creator, community, entrepreneurship). Free tier: 5 questions/day per email. Upgrade at tomosborne.me/cmo.

ParametersJSON Schema
NameRequiredDescriptionDefault
questionYesWhat you want to ask Tom Osborne's second brain. Examples: 'How do I get to my first 100 customers as a DTC brand?', 'What's Tom's view on bootstrapping a SaaS to first revenue?', 'What worked at AllDomains for the Eclipse SVM launch?'

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses knowledge sources (100-question interview corpus, 15 years memory, 21k articles across 17 verticals), output format (Tom's voice), and free tier restriction (5 questions/day per email). No annotations provided, but description compensates well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is informative but slightly verbose. It is well-structured, starting with the purpose and ending with usage limits and upgrade link.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema or siblings, description fully covers what the tool does, its capabilities, limitations, and even includes upgrade information. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single 'question' parameter with schema coverage 100%. Description adds context about what types of questions are suitable and the knowledge base, but does not add significant parameter semantics beyond schema examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly identifies the action (ask a question), resource (Tom Osborne's second brain), and domain (marketing, growth, etc.). It distinguishes the tool by specifying the knowledge sources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes appropriate topics and free tier limit, but does not explicitly state when not to use the tool or provide alternatives. With no siblings, this is acceptable but missing some guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedask_tom

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so no ambiguity between tools. The tool's purpose is clearly defined as asking Tom's brain a question.

Naming Consistency5/5

With a single tool named 'ask_tom' (verb_noun), naming is trivially consistent and follows a clear pattern.

Tool Count3/5

One tool for a broad domain (marketing, growth, etc.) feels thin, but it aligns with the server's focused purpose of Q&A. Still borderline low.

Completeness4/5

The single tool covers the primary use case of asking questions and returning answers. Minor gaps like advanced filtering or knowledge management are not expected for this specific server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    Personal RAG database and semantic search built from inside your AI chat. Store knowledge, voice, and skills; Claude and ChatGPT create work that sounds like you.
    -
  • A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to check brand mentions across AI search surfaces like ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews using natural language queries.
    4
    3
    1
    MIT
  • F
    license
    A
    quality
    B
    maintenance
    Enables LLMs to access a user's personal writing context—voice, style, opinions, expertise, projects, and communication patterns—via curated markdown files, helping the LLM match the user's voice when generating written content.
    2
    3
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DegenDoes/second-brain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server