Bucketeer Docs Local MCP Server

Created By
bucketeer-ioa year ago
Local MCP Server to query Bucketeer documentation
Overview

What is Bucketeer Docs Local MCP Server?

Bucketeer Docs Local MCP Server is a Model Context Protocol (MCP) server designed to query and retrieve documentation from Bucketeer's feature flag and experimentation platform, enabling AI assistants to provide accurate information about Bucketeer's features and usage.

How to use Bucketeer Docs Local MCP Server?

To use the server, clone the repository, install dependencies, build the project, and start the server. You can also use it with npx for easier setup.

Key features of Bucketeer Docs Local MCP Server?

  • Automatically fetches and indexes documentation from the Bucketeer GitHub repository.
  • Supports intelligent indexing with keyword extraction and relevance scoring.
  • Provides search functionality and document retrieval through the MCP interface.

Use cases of Bucketeer Docs Local MCP Server?

  1. Enabling AI assistants to access and provide documentation on Bucketeer features.
  2. Searching for specific documentation related to feature flags and experiments.
  3. Integrating with other tools that utilize the Model Context Protocol for documentation access.

FAQ from Bucketeer Docs Local MCP Server?

  • Can I use this server for other documentation?

No, it is specifically designed for Bucketeer documentation.

  • Is there a way to force rebuild the index?

Yes, you can use the command npm run build:index:force to force a rebuild of the index.

  • What are the system requirements?

You need Node.js 18+ and npm to run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bucketeer-io
Star
1
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago