Second Brain MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOM_API_BASE | No | Override the API base (only useful for dev/testing) | https://tomosborne.me |
| 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) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so no ambiguity between tools. The tool's purpose is clearly defined as asking Tom's brain a question.
With a single tool named 'ask_tom' (verb_noun), naming is trivially consistent and follows a clear pattern.
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.
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.