toggle-brain MCP Server
Provides access to the Toggle Brain knowledge base, including resources, prompt templates, and executable scripts from the toggle-brain repository.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@toggle-brain MCP Serversummarise the Toggle Brain positioning docs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
toggle-brain MCP Server
A Model Context Protocol server that exposes the Toggle Brain knowledge base, prompt templates, and executable scripts to any MCP-compatible AI assistant — Claude Code, Cursor, Windsurf, and more.
Content lives in the toggle-brain repository and is automatically synced here on every push. You never need a GitHub token, API keys, or manual updates at runtime — just clone, build, and connect.
What it exposes
MCP primitive | Source in toggle-brain | Example |
Resources |
|
|
Prompts |
|
|
Tools | Any |
|
Related MCP server: Weft
Prerequisites
Node.js 20 LTS or later
That's it. No tokens, no API keys, no external services.
Setup
1. Clone the repo
git clone https://github.com/toggle-workspace/toggle-mcp.git
cd toggle-mcp2. Install dependencies and build
npm install
npm run build3. Verify it works
node dist/index.js
# Loaded: 153 resources, 15 prompts, 1 toolsConnecting to Claude Code
From inside the cloned toggle-mcp directory, run:
claude mcp add toggle-brain node "$(pwd)/dist/index.js"Then run /mcp inside a Claude Code session to confirm it is connected:
/mcp
# toggle-brain — ConnectedConnecting to Cursor
Add to ~/.cursor/mcp.json (or via Cursor Settings → MCP):
{
"mcpServers": {
"toggle-brain": {
"command": "node",
"args": ["/path/to/toggle-mcp/dist/index.js"]
}
}
}Replace /path/to/toggle-mcp with the actual path where you cloned the repo.
Connecting to Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"toggle-brain": {
"command": "node",
"args": ["/path/to/toggle-mcp/dist/index.js"]
}
}
}Replace /path/to/toggle-mcp with the actual path where you cloned the repo.
Remote / HTTP mode
Set TRANSPORT=http to run as an SSE server on a fixed port:
TRANSPORT=http PORT=3000 node dist/index.jsPoint any MCP client at http://localhost:3000/sse.
Usage
Once connected, the AI assistant can:
Browse knowledge — ask it to read resources like "summarise the Toggle Brain positioning docs" or reference
kb://brain--services--copywritingdirectlyRun prompt templates — ask it to use a prompt like
generators--email-sequencewith your variables filled inExecute tools — any
.tsor.pyscripts from toggle-brain are callable as tools
In Claude Code, confirm what is loaded at any time:
/mcpFor maintainers
How the sync works
Content in this repo is kept up to date by a two-step GitHub Actions pipeline:
toggle-brain runs
.github/workflows/notify-mcp.ymlon every push tomain. This workflow dispatches arepository_dispatchevent of typetoggle-brain-updatedto thetoggle-mcprepository.toggle-mcp has
.github/workflows/sync-brain.ymlwhich listens for that event, checks out toggle-brain, copies its contents into this repo, and commits and pushes the result.
The MCP server reads from the local content/ directory at runtime — no network calls, no tokens required for end users.
Required secret
The toggle-brain notify workflow needs a GitHub PAT stored as a repository secret named GH_PAT. This token must have:
repo scope (to dispatch events to toggle-mcp)
workflow scope (to trigger Actions workflows)
Add it at: toggle-brain repo → Settings → Secrets and variables → Actions → New repository secret
Adding the notify workflow to toggle-brain
See TOGGLE_BRAIN_SETUP.md for the step-by-step guide. In short, create .github/workflows/notify-mcp.yml in the toggle-brain repository with the content from toggle-brain-notify-workflow.yml in this repo.
Once this is in place, every push to toggle-brain/main will automatically update the content in this repo within seconds.
Troubleshooting
Symptom | Fix |
| Re-run |
Resources show as empty or missing | Run |
Build fails with type errors | Ensure Node.js 20 or later is installed ( |
Sync Action fails in toggle-brain | Check that the |
Sync Action fails in toggle-mcp | Check that |
HTTP mode not reachable | Confirm |
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
- tools_remotion_remotion.configD
- tools_remotion_src_indexD
- tools_remotion_src_onboarding_registryD
- tools_remotion_src_onboarding_videos_welcomeC
- tools_remotion_src_onboarding_videos_tiktok_adsD
- tools_remotion_src_onboarding_videos_seoD
- tools_remotion_src_onboarding_videos_permissionsD
- tools_remotion_src_onboarding_videos_meta_adsD
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/toggle-workspace/toggle-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server