Claude Connect

An MCP-compliant external connector server enabling Claude and other LLMs to interact with web APIs, filesystem, and custom resources. v1.1 (March 2025)

Overview

Claude Connect is a server that implements Anthropic's Model Context Protocol (MCP), allowing Large Language Models like Claude to interact with external tools and resources in a standardized way. This server enables LLMs to access web search results, read and write files in a sandboxed environment, and utilize custom resources.

Key Features

- Web Search Integration: Connect to Bing Search API (required) and Google Search API (optional)
- File Operations: Read, write, list, and delete files within a secure sandbox
- Custom Resources: Define and access custom resource types
- Prompt Templates: Store and retrieve custom prompt templates
- Multiple Transport Options: Primary STDIO transport for Claude Desktop integration, optional HTTP transport with JWT authentication
- Extensible Architecture: Easy to add new capabilities and resources
- Cross-Platform: Tested on Windows 10, but designed to work on any platform supporting Python 3.10+

Quick Start

This MCP server enables Large Language Models like Claude to access external tools and resources. It takes about 15 minutes to set up and requires Python 3.10+ and API keys for search functionality. Follow these steps to get started:

1. Install Python 3.10+, create a virtual environment, and activate it (e.g., using python -m venv venv and ..\venv\Scripts\activate on Windows).
2. Install dependencies: ..\venv\Scripts\pip.exe install -r requirements.txt (using full path helps bypass potential PowerShell execution policy issues).
3. Rename .env.example to .env and add your API keys (Bing Search API required, Google Search API optional).
4. Run server in STDIO mode: ..\venv\Scripts\python.exe main.py or HTTP mode: ..\venv\Scripts\python.exe main.py --http.
5. Test with ..\venv\Scripts\pytest.exe.

Note: Some commands, especially activation or installation, might require running PowerShell/CMD as Administrator on Windows depending on your system configuration.

For detailed setup instructions, see the Setup Guide. For Claude Desktop integration, see the Claude Desktop Integration Guide.

Documentation

- Setup Guide
- Configuration Guide
- Claude Desktop Integration
- API Reference
- Advanced Usage
- Troubleshooting

Advanced Usage

For advanced usage scenarios, including:

- Manual JSON-RPC interaction
- Extending the server with new capabilities
- Using PostgreSQL instead of SQLite
- Enabling Redis caching
- Internationalization
- Performance tuning

See the Advanced Usage Guide.

Code Explanation & Design Rationale

The Claude Connect server is designed with the following principles in mind:

- Modularity: Each capability is implemented as a separate handler function.
- Security: File operations are restricted to a sandbox directory, and path traversal attempts are prevented.
- Extensibility: New capabilities can be added by implementing new handler functions and updating the capabilities list.
- Configurability: Most aspects of the server can be configured through environment variables and configuration files.

The server supports two transport modes:

- STDIO: For integration with Claude Desktop and other MCP clients that support STDIO transport.
- HTTP: For development, testing, and integration with web applications.

For more details on the code structure and design decisions, see the API Reference.

Containerization & Deployment

You can containerize Claude Connect using Docker:

```dockerfile