@beachio/gleo-mcp

MCP bridge for connecting Claude Desktop, Cursor, and other MCP-compatible clients to the Gleo API.

What it does

This bridge runs locally as a stdio process. Your MCP client (Claude Desktop, Cursor, etc.) launches it, and it forwards JSON-RPC calls to the Gleo HTTP API using your personal API token.

Requirements

• Node.js 18 or later
• A Gleo account with an MCP token (see Setup below)

Setup

1. Generate an MCP token

1. Sign in to Gleo and go to Settings > Developer
2. Under MCP Tokens, click Create new token
3. Give it a label (e.g. "My Cursor Setup") and click Create
4. Copy the token — it is only shown once

2. Configure your MCP client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "gleo": {
      "command": "npx",
      "args": ["-y", "@beachio/gleo-mcp"],
      "env": {
        "GLEO_TOKEN": "gleo_mcp_your_token_here"
      }
    }
  }
}

Restart Claude Desktop after saving.

Cursor

Edit .cursor/mcp.json in your project root, or the global Cursor MCP config:

{
  "mcpServers": {
    "gleo": {
      "command": "npx",
      "args": ["-y", "@beachio/gleo-mcp"],
      "env": {
        "GLEO_TOKEN": "gleo_mcp_your_token_here"
      }
    }
  }
}

Global install (optional)

If you prefer not to use npx each time:

npm install -g @beachio/gleo-mcp

Then use "command": "gleo-mcp" instead of "command": "npx" / "args": ["-y", "@beachio/gleo-mcp"].

Environment variables

| Variable | Required | Default | Description | |---|---|---|---| | GLEO_TOKEN | Yes | — | Your MCP API token from Gleo Settings | | GLEO_API_URL | No | https://api.gleo.com/mcp | Override the API endpoint |

Available tools

The bridge exposes all Gleo MCP tools, including:

• get_artifact, search_artifacts, create_artifact, semantic_search_artifacts
• list_sessions, get_session, create_session
• list_playbooks, get_playbook, create_playbook_session
• list_playbook_templates, get_playbook_template
• list_playbook_questions, create_playbook_question, add_playbook_question_answer
• list_playbook_tasks, create_playbook_task
• create_agenda_item, create_agenda_items, update_agenda_item, delete_agenda_item
• create_prep_activity, create_prep_activities
• list_playbook_artifacts, create_playbook_artifact
• link_artifact_to_source
• list_playbook_question_tags, attach_question_tag, detach_question_tag
• toggle_playbook_question_reaction

Troubleshooting

"GLEO_TOKEN environment variable is required" — set the GLEO_TOKEN env var in your MCP client config.

"Invalid token" — verify the token was copied correctly and has not been deleted or regenerated in Gleo Settings.

Timeout errors — check your network connection to api.gleo.com.

License

MIT