MCP server exposing LanternBRP Gateway APIs as AI-agent tools.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"brp-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# LanternBRP MCP Server MCP server that exposes LanternBRP Gateway APIs as AI-agent tools. Works with Cursor, Claude Desktop, and any MCP-compatible AI host. ## Build & Publish (for maintainers) ```bash cd brp_mcp_python_package/ # Install build tools (one-time) pip install build twine # Build the package python -m build # Upload to PyPI twine upload dist/* ``` This creates `dist/brp_mcp-<version>-py3-none-any.whl` and `dist/brp_mcp-<version>.tar.gz`. After publishing, all users get the update via `uvx --upgrade brp-mcp`. To bump the version before a release, edit `version` in `pyproject.toml`: ```toml [project] version = "0.2.1" ``` ## Quick Start (for AI-agent users) Add this to your MCP config (e.g. Cursor's `mcp.json` or Claude Desktop's config): ```json { "brp_mcp_server": { "command": "uvx", "args": ["--upgrade", "brp-mcp"], "env": { "BRP_ENV": "dev", "BRP_AUTH0_CLIENT_ID": "<your-client-id>", "BRP_AUTH0_CLIENT_SECRET": "<your-client-secret>" } } } ``` That's it. The server auto-resolves gateway URLs, Auth0 domain, audience, tool descriptions, and visibility from the bundled config based on `BRP_ENV`. ## How It Works ``` AI Agent (Cursor / Claude Desktop) ↕ MCP Protocol (stdio) brp-mcp server (local subprocess) ↕ HTTPS (Auth0 bearer token) LanternBRP Gateway API ``` 1. The AI host spawns `brp-mcp` as a child process via `uvx` 2. The server fetches the LanternBRP Gateway's OpenAPI spec over HTTP 3. It registers one MCP tool per visible API endpoint 4. Tool descriptions are enriched with N8N-style domain instructions 5. When the AI calls a tool, the server makes an authenticated HTTP request to the Gateway 6. Auth0 M2M tokens are obtained automatically using the provided client credentials ### Bundled Config All config files are shipped inside the Python package: | File | Purpose | |------|---------| | `bundled_config/env_profiles.json` | Gateway URLs + Auth0 domain/audience per environment | | …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.