holaspirit

The holaspirit-mcp-server exposes a set of MCP tools that bridge your Holaspirit data to AI assistants through a standardized MCP interface. It provides operations to list and fetch data about tasks, metrics, circles, roles, domains, policies, meetings, and members, as well as to retrieve details for specific circles, roles, meetings, and member feeds. By using the MCP protocol, clients can issue structured requests to the server and receive consistent responses, enabling seamless integration of Holaspirit data into your AI workflows.

To run the server in standard input/output (stdio) mode, start the server normally and connect via MCP clients that communicate over stdin/stdout. For HTTP-based integrations, start the HTTP transport, which serves requests over a web protocol and supports the latest Streamable HTTP transport. The server uses your Holaspirit API token and organization ID to access data from Holaspirit and translate it into MCP-compatible responses. Typical use involves configuring the client to target the server and calling listed MCP tools such as holaspirit_list_tasks, holaspirit_get_circle, holaspirit_search_member, and others to retrieve or query data as needed.

Prerequisites:

• Node.js and npm installed on your machine
• Access to a Holaspirit API token and organization ID

Installation (recommended via Smithery):

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

Manual installation (npm):

npm install holaspirit-mcp-server

Configuration: create or edit environment variables to provide Holaspirit credentials.

# Example environment setup (env or .env file)
export HOLASPIRIT_API_TOKEN=your_api_token_here
export HOLASPIRIT_ORGANIZATION_ID=your_organization_id_here

Usage examples:

# Stdio transport (default)
npx holaspirit-mcp-server

# HTTP transport (listen on port 3000)
npx holaspirit-mcp-server --port 3000

Environment variables are required for API access. If you use a .env file, copy the example and fill in your values:

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

Common issues:

• Invalid or missing API token: ensure the token has read access to the organization data.
• Network or API rate limits: consider adding retries or handling rate limits in client code.
• Port conflicts on HTTP transport: ensure the port you specify is available or choose another port.

Transport options:

• StdIO (default) for MCP clients that communicate via stdin/stdout.
• HTTP transport for web clients; supports the Streamable HTTP protocol.

NPM package: holaspirit-mcp-server. If you publish or deploy, you can pin a specific version to ensure stability.