Back to MCP directory
publicPublicdnsLocal runtime

holaspirit-mcp-server

提供与MCP兼容的访问Holaspirit API的方式,允许AI助手通过标准化接口与组织数据(如任务、圈子、角色和会议)进行交互。

article

README

holaspirit-mcp-server

smithery badge npm version

A MCP(Model Context Protocol) server that accesses to Holaspirit API.

This server provides MCP-compatible access to Holaspirit's API, allowing AI assistants to interact with your Holaspirit data through a standardized interface.

Holaspirit Server MCP server

Features

Available tools:

  • holaspirit_list_tasks - List all tasks in the organization
  • holaspirit_list_metrics - List all metrics in the organization
  • holaspirit_list_circles - List all circles in the organization
  • holaspirit_get_circle - Get details of a specific circle
  • holaspirit_list_roles - List all roles in the organization
  • holaspirit_get_role - Get details of a specific role
  • holaspirit_list_domains - List all domains in the organization
  • holaspirit_list_policies - List all policies in the organization
  • holaspirit_list_meetings - List all meetings in the organization
  • holaspirit_get_meeting - Get details of a specific meeting
  • holaspirit_get_member_feed - Get member feed
  • holaspirit_get_tensions - Get tensions for a meeting or meetings
  • holaspirit_search_member - Search for a member by email

Quick Start

Installation

Installing via Smithery

To install holaspirit-mcp-server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install holaspirit-mcp-server --client claude

Manual Installation

npm install holaspirit-mcp-server

Configuration

You can configure the server using environment variables. Two methods are supported:

Environment Variables

  • HOLASPIRIT_API_TOKEN: Your Holaspirit API token
  • HOLASPIRIT_ORGANIZATION_ID: Your Holaspirit organization ID

Using .env File

Create a .env file in the project root:

# Copy the example file
cp .env.example .env

Then edit .env with your actual values:

HOLASPIRIT_API_TOKEN=your_api_token_here
HOLASPIRIT_ORGANIZATION_ID=your_organization_id_here

Usage

The server supports two transport modes:

Stdio Transport (Default)

For use with MCP clients that communicate via stdin/stdout:

npx holaspirit-mcp-server

HTTP Transport

For use with web clients or HTTP-based integrations using the latest Streamable HTTP protocol:

npx holaspirit-mcp-server --port 3000

The HTTP server accepts POST requests only on any path (e.g., /, /mcp, /sse) and uses the Streamable HTTP transport protocol.

Edit MCP configuration json for your client:

For stdio transport:

...
    "holaspirit": {
      "command": "npx",
      "args": [
        "-y",
        "holaspirit-mcp-server"
      ],
      "env": {
        "HOLASPIRIT_API_TOKEN": "<your token>",
        "HOLASPIRIT_ORGANIZATION_ID": "<your org id>"
      }
    },
...

For HTTP transport, configure your client to connect to:

  • http://localhost:3000/ (or any path)

Development

Available Scripts

  • npm run dev - Start the server in development mode with hot reloading
  • npm run build - Build the project for production
  • npm run start - Start the production server
  • npm run lint - Run linting checks (ESLint and Prettier)
  • npm run fix - Automatically fix linting issues
  • npm run examples - Run the example scripts

Contributing

  1. Fork the repository
  2. Create your feature branch
  3. Run tests and linting: npm run lint
  4. Commit your changes
  5. Push to the branch
  6. Create a Pull Request
help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client