Skip to main content
Toolbox installed servers Toolbox is where you manage MCP servers in your workspace. Install servers from the community registry to give your playbooks access to external APIs, databases, and services.

​
What is the Toolbox?

The Toolbox provides:
  • Browse Catalog: Explore available MCP servers from the NimbleBrain registry
  • One-Click Install: Install servers instantly without configuration
  • Server Management: View status, logs, and control installed servers
  • Integration with Playbooks: All installed servers are available to your playbooks

​
Installed Servers

The Installed Servers tab shows all MCP servers currently running in your workspace: Toolbox installed servers view

​
Server Information

Each server card displays:
  • Server name: The display name of the MCP server
  • Description: What the server does and which APIs it provides
  • Status: Running status indicator (🟢 Running)
  • Package ID: The registry identifier (e.g., ai.nimbletools/echo)

​
Server Actions

​
Connect
Generate connection configuration for Claude Desktop or other MCP clients
​
Logs
View real-time logs from the server to debug issues
​
Restart
Restart the server if it becomes unresponsive
​
Uninstall
Remove the server from your workspace
​
Configure
Manage server-specific settings and environment variables

​
Browse Catalog

Toolbox catalog browser The catalog contains MCP servers from the NimbleBrain community registry.

​
Filter by Category

Servers are organized into categories:

All

View all available servers

Data Intelligence

APIs for financial data, web search, and intelligence

Developer Tools

GitHub, reverse text, documentation search

Infrastructure Data

Database access (PostgreSQL, ClickHouse)

​
Server Cards

Each server in the catalog shows:
  • Server icon: Visual identifier
  • Server name: Display name
  • Package ID: Full registry identifier with version
  • Description: What the server provides
  • Category badge: Which category it belongs to
  • Install button: One-click installation

​
Installing a Server

1

Browse Catalog

Click the “Browse Catalog” tab in Toolbox
2

Find a Server

Scroll through or use the category filters to find a server
3

Review Details

Click on a server card to see full details (optional)
4

Click Install

Click the blue “Install” button on the server card
5

Wait for Installation

The server will be installed and started automatically (usually 5-15 seconds)
Once installed, the server is immediately available to all playbooks in your workspace!

​
Available Servers

Here are some popular MCP servers in the catalog:

​
Data Intelligence

Financial market data API with real-time quotes, company profiles, and news. Requires API key from Finnhub.
Real-time web search, extract, map & crawl capabilities for web intelligence. Requires Tavily API key.
IP geolocation, network intelligence, ASN lookup, privacy detection, and WHOIS queries.
U.S. National Parks Service API for park information, alerts, campgrounds, and events.

​
Developer Tools

Interact with GitHub repos, issues, PRs, code search, and Actions through natural language. Requires GitHub token.
Simple echo service for testing MCP protocol functionality, debugging, and development workflows.
Token-efficient documentation search for AI agents with web content extraction.
Text manipulation service with reverse and analysis tools for processing and transforming text data.

​
Infrastructure Data

PostgreSQL MCP server with configurable read/write access and performance analysis. Requires database credentials.
OLAP database for real-time analytics and data warehousing queries. Requires ClickHouse connection details.

​
Server Configuration

Some servers require configuration before they can be used:

​
API Keys & Secrets

Servers that connect to external APIs need authentication:
  1. Click the Configure button (gear icon) on the server card
  2. Enter required API keys or credentials
  3. Save the configuration
  4. Restart the server if prompted
Security: API keys are encrypted and stored securely. They are never exposed in logs or visible to other workspace members.

​
Environment Variables

Some servers accept optional configuration via environment variables:
  • Connection timeouts
  • Rate limiting
  • Feature flags
  • Custom endpoints
Check the server documentation for available options.

​
Server Logs

View real-time logs to debug issues:
1

Click Logs

Click the “Logs” button on any installed server
2

View Output

See real-time stdout/stderr from the server
3

Filter Logs

Use the search box to filter log messages
4

Download

Export logs for offline analysis

​
Connecting to Claude Desktop

Generate a connection configuration for any installed server:
1

Click Connect

Click the “Connect” button on the server card
2

Copy Configuration

Copy the generated JSON configuration
3

Open Claude Config

Open your Claude Desktop configuration file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
4

Add Configuration

Merge the configuration into your existing config file
5

Restart Claude

Quit and restart Claude Desktop
The connection config includes your workspace API token for authentication. Keep it secure!

​
Server Status

🟢 Running

Server is healthy and responding to requests

🔴 Error

Server failed to start or is not responding

🟡 Installing

Server is being installed or restarted

⚫ Stopped

Server is installed but not running

​
Uninstalling a Server

1

Click Uninstall

Click the red “Uninstall” button on the server card
2

Confirm

Confirm that you want to remove the server
3

Cleanup

The server and its configuration will be removed
Warning: Uninstalling a server will break any playbooks that depend on it. Make sure no playbooks are using the server before uninstalling.

​
Troubleshooting

  • Check that you have sufficient workspace resources
  • Try refreshing the catalog
  • Check the Activity Logs for error details
  • Click “Logs” to see error messages
  • Check if API keys are configured correctly
  • Try restarting the server
  • Verify the server shows “Running” status
  • Try restarting the server
  • Check that the server is installed in the correct workspace
  • Verify the API key is valid
  • Check that the key has the necessary permissions
  • Make sure you saved the configuration after entering the key

​
Best Practices

Install What You Need

Only install servers that your playbooks will use

Secure API Keys

Never share API keys or workspace tokens publicly

Monitor Logs

Check logs when debugging playbook issues

Test Connections

Verify servers work before using them in production playbooks

Playbooks

Create workflows that use your installed MCP servers

API Tokens

Generate tokens for Claude Desktop integration

Activity Logs

Track server installations and configuration changes

Claude Desktop Setup

Connect your servers to Claude Desktop
⌘I