Claude Desktop Setup Guide | Bootspring Docs

MCP Server Status
=================

Server: bootspring
Status: Configured ✓
Config: ~/.config/Claude/claude_desktop_config.json

Connection test: Success ✓
Available tools: 12
Available resources: 3

Tools:
  ✓ bootspring_context
  ✓ bootspring_agent
  ✓ bootspring_skill
  ✓ bootspring_workflow
  ...

Manual Configuration#

If automatic setup fails, configure manually.

macOS: Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

Windows: Edit %APPDATA%\Claude\claude_desktop_config.json:

Linux: Edit ~/.config/Claude/claude_desktop_config.json:

Loading code block...

Restart Claude Desktop#

After configuration, restart Claude Desktop:

Quit Claude Desktop completely
Relaunch the application
Check for "bootspring" in the tools menu

Available MCP Tools#

bootspring_context#

Get project context and understanding.

Usage in Claude:

Use bootspring_context to understand the project structure.

Returns:

Project overview
Tech stack
Architecture summary
Key files and patterns

bootspring_agent#

Invoke expert agents for specialized tasks.

Usage in Claude:

Use bootspring_agent to invoke the security-expert and review the authentication flow.

Available agents:

frontend-expert
backend-expert
database-expert
security-expert
performance-expert
testing-expert
And 30+ more

bootspring_skill#

Apply skill patterns to generate code.

Usage in Claude:

Use bootspring_skill to apply the api-endpoint pattern for a user registration endpoint.

Available patterns:

patterns/api-endpoint
patterns/react-component
patterns/prisma-crud
auth/jwt
And 50+ more

bootspring_workflow#

Start and manage development workflows.

Usage in Claude:

Use bootspring_workflow to start the feature-development workflow for implementing user notifications.

Available workflows:

preseed - Idea to documentation
seed - Project scaffolding
feature-development - Full feature lifecycle
security-audit - Security review
And more

bootspring_generate#

Regenerate project context.

Usage in Claude:

Use bootspring_generate to update the project context after recent changes.

bootspring_quality#

Run quality checks.

Usage in Claude:

Use bootspring_quality with the pre-commit preset to check code quality.

bootspring_todo#

Manage project todos and tasks.

Usage in Claude:

Use bootspring_todo to add "Implement error handling" to the task list.

MCP Resources#

project://context#

Access current project context.

Usage:

Read the project://context resource to understand the codebase.

project://config#

Access Bootspring configuration.

Usage:

Read project://config to see available agents and settings.

project://agents#

List available agents and their capabilities.

Usage:

Read project://agents to see which experts I can invoke.

Using Bootspring in Claude#

Basic Workflow#

Start a conversation about your project
Request context: "Use bootspring_context to understand my project"
Get help: "Use bootspring_agent to invoke the frontend-expert for this component"
Apply patterns: "Use bootspring_skill to apply the form-validation pattern"

Example Conversations#

Understanding the codebase:

User: I'm working on a Next.js project. Help me understand the architecture.

Claude: I'll use the project context to understand your codebase.
[Uses bootspring_context]

Based on the context, your project is a Next.js 14 application with:
- App Router architecture
- Prisma for database (PostgreSQL)
- JWT sessions for authentication
- Tailwind CSS for styling

The main routes are...

Getting expert help:

User: I need to optimize my database queries. They're getting slow.

Claude: Let me invoke the database expert to analyze this.
[Uses bootspring_agent: database-expert]

The database expert recommends:
1. Add indexes on frequently queried columns
2. Use connection pooling
3. Implement query result caching
...

Applying patterns:

User: Create a new API endpoint for user preferences.

Claude: I'll apply the API endpoint pattern for this.
[Uses bootspring_skill: patterns/api-endpoint]

Here's the endpoint following your project's patterns:
[Generated code]

Configuration Options#

API Key Management#

Environment variable (recommended for CI):

Loading code block...

Direct key (for personal use):

Loading code block...

Custom Node Path#

If Node.js isn't in the default path:

Loading code block...

nvm Users#

For nvm installations:

macOS/Linux:

Loading code block...

Project-Specific Configuration#

For project-specific settings:

Loading code block...

Multiple Projects#

Project Switching#

Claude Desktop uses the current working directory. To switch projects:

Open a new conversation
Ask Claude to read context from a specific directory

Or configure multiple servers:

Loading code block...

Troubleshooting#

MCP Server Not Appearing#

Check configuration file exists

Loading code block...
Validate JSON syntax

Loading code block...
Restart Claude Desktop completely
Check logs
- macOS: ~/Library/Logs/Claude/
- Windows: %LOCALAPPDATA%\Claude\logs\
- Linux: ~/.local/share/Claude/logs/