Access Holaspirit Organizational Data

Gives AI assistants read access to Holaspirit's organizational data - the platform for running Holacracy and self-management structures - through 13 MCP tools: listing tasks, metrics, circles, roles, domains, policies, and meetings; getting details of a specific circle, role, or meeting; fetching a member's feed; getting tensions raised for one or more meetings; and searching for a member by email. The server supports two transport modes: stdio by default for MCP clients that talk over stdin/stdout, or an HTTP transport using the Streamable HTTP protocol, started with a port flag, which accepts POST requests on any path.

Use it when an AI assistant needs to read an organization's Holaspirit structure - its circles, roles, policies, tasks, metrics, meetings, and tensions - conversationally instead of through the Holaspirit web UI. Configuration needs two values, a Holaspirit API token and an organization ID, supplied either as environment variables directly or via a .env file copied from the project's example and filled in. Installation is either automatic through Smithery for Claude Desktop, or a manual npm install, and the project also ships development scripts for hot-reloading, building, linting with ESLint and Prettier, and running example scripts, for anyone contributing rather than just consuming it.

Read access to an organization's full Holaspirit graph: holaspirit_list_tasks and holaspirit_list_metrics for org-wide task and metric listings, holaspirit_list_circles plus holaspirit_get_circle for circle listing and detail, holaspirit_list_roles plus holaspirit_get_role for role listing and detail, holaspirit_list_domains and holaspirit_list_policies for governance artifacts, holaspirit_list_meetings plus holaspirit_get_meeting for meeting listing and detail, holaspirit_get_member_feed for a member's activity feed, holaspirit_get_tensions for tensions raised in one or more meetings, and holaspirit_search_member for finding a member by email address.

Install automatically via Smithery for Claude Desktop, or npm install holaspirit-mcp-server manually, then set the token and organization ID and register the server for stdio transport:

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

or run it with a --port flag and connect the client to that address for HTTP transport instead.

Teams running Holaspirit who want an AI assistant to answer questions about their circle structure, roles, meetings, and tensions directly, instead of navigating the Holaspirit app. The project also welcomes contributions through a standard fork-branch-lint-PR workflow, running its own lint and fix scripts (ESLint and Prettier) before a pull request is expected to pass review, alongside a dedicated development-mode script for hot-reloading changes and a separate production build/start pair reserved specifically for deployment.