Boost.space MCP Server Proxy for Claude Desktop
Proxy Boost.Space's REST API with an MCP server for Claude Desktop, enabling seamless MCP client integration and access to Boost.Space features.
npx -y @boostspace/boostspace-mcp-serverOverview
Boost.space MCP Server is a lightweight Model Context Protocol (MCP) proxy that exposes Boost.Space’s REST API to MCP-compatible clients such as Claude Desktop. It translates MCP tool requests into Boost.Space API calls, enabling language models and other MCP clients to access Boost.Space resources (spaces, items, comments, attachments, etc.) through the MCP tooling interface without needing direct REST integration.
This proxy is useful when you want to integrate Boost.Space into an assistant workflow that expects MCP tools rather than raw HTTP calls. By running the server locally and configuring an MCP client (e.g., Claude Desktop) to use it, models can call Boost.Space functionality via the standardized MCP interface while the proxy handles authentication and HTTP details.
Features
- Proxies Boost.Space REST API calls into MCP-compatible tool invocations
- Simple install via pip or uv (astral.sh)
- Minimal configuration with two environment variables (API base and token)
- StdIO transport support for easy integration with Claude Desktop
- Meant for development, local usage, and embedding Boost.Space features into MCP clients
Installation / Configuration
Install from PyPI:
Install with uv (astral.sh):
|
Run the server
# Run via python module (recommended for local/dev)
# Run with uv
Environment variables
Set the following environment variables before starting the server:
- BOOSTSPACE_API_BASE — Base URL for Boost.Space REST API (e.g., https://api.boost.space)
- BOOSTSPACE_TOKEN — Bearer token used to authenticate API requests
Example (Unix):
Claude Desktop configuration
Add an MCP server entry to Claude Desktop’s config to use the proxy via stdio:
"mcpServers": {
"boostspace": {
"command": "python",
"args": ["-m","boostspace_mcp.server"],
"env": {
"BOOSTSPACE_API_BASE": "{{API_PATH}}",
"BOOSTSPACE_TOKEN": "{{TOKEN}}"
},
"transport": "stdio"
}
}
Replace {{API_PATH}} and {{TOKEN}} with your Boost.Space API base and bearer token. Restart Claude Desktop after editing the config.
Available Resources
The proxy exposes Boost.Space functionality through MCP tools. Internally it forwards MCP tool calls to Boost.Space REST endpoints and returns structured results for the client. Common resource types that are typically accessible via the proxy include:
- Spaces and collections
- Items / documents within a space
- Search over items or documents
- Comments and activity
- Attachments / files
Environment variables
| Variable | Description |
|---|---|
| BOOSTSPACE_API_BASE | Base URL for Boost.Space REST API |
| BOOSTSPACE_TOKEN | Bearer token for API authentication |
Source code and issues: https://github.com/boostspace/boostspace-mcp-server
Use Cases
- Enable a Claude Desktop assistant to search your Boost.Space workspace and summarize matching documents for users.
- Let a model create or update an item/task in Boost.Space as part of an automated workflow (e.g., capture meeting notes as a new item).
- Provide the model with contextual documents from Boost.Space to improve relevance when generating responses.
- Integrate Boost.Space data into multi-tool chains where the assistant queries Boost.Space, processes results, and calls other MCP tools.
Concrete example: Summarize latest items
- Start the MCP server with your API base and token.
- Configure Claude Desktop to include the boostspace MCP server.
- Ask the assistant: “Search Boost.Space for items about ‘Q2 roadmap’ and summarize the top 3 results.” The assistant will call the proxy tool, which executes the Boost.Space search and returns the data for summarization.
Development & Testing
For contributors and local development:
# Install dev dependencies
# Run tests
# Linting
The project follows standard Python packaging and can be extended to add handling for specific Boost.Space endpoints or to customize response formats for MCP clients.
Notes and Best Practices
- Keep your BOOSTSPACE_TOKEN secret and only provide it to trusted local environments or clients.
- The proxy is intended primarily for local and developer-facing integrations. For production, ensure network and token security according to your organization’s policies.
- If you need additional Boost.Space endpoints proxied, extend the server by following the repository’s contribution guidelines and tests.