MCP server exposing the Modern-Expo virtual Business Analyst Knowledge Base (read/derive 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":"ba-agent-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.
# ba-agent-mcp An [MCP](https://modelcontextprotocol.io) server that exposes the Modern-Expo virtual **Business Analyst Knowledge Base** as a small set of **read / derive** tools. It never writes to SUPPA Docs or the Knowledge Base and is deliberately kept off the governed write path — authoring documents goes through the human-gated `business-analyst` skill, not this server. ## Install ```bash uvx ba-agent-mcp # run on demand in an isolated environment (recommended) # or pip install ba-agent-mcp # then run: ba-agent-mcp ``` ## Credentials — you supply your own **This package ships no credentials.** Each user provides their **own** keys and their **own** SUPPA identity. Nothing is ever read from the MCP client JSON config; secrets are resolved from the environment, in this order: 1. real environment variables in the launching shell, then 2. an explicit env file at `$BA_AGENT_ENV_FILE`, then 3. `~/.ba-agent/.env` ```bash # ~/.ba-agent/.env (or export these in your shell) SUPABASE_URL=https://<your-project>.supabase.co SUPABASE_SERVICE_ROLE_KEY=... # or SUPABASE_ANON_KEY for read-only SUPPA_API_KEY=... # your own SUPPA identity (or SUPPA_TOKEN) GEMINI_API_KEY=... # optional — enables hybrid (vector) search FIGMA_TOKEN=... # optional — enables analyze_figma ``` > Never put any secret in the MCP client JSON. A tool whose credentials are > absent returns a clear, structured error instead of failing the server, so you > can add capabilities incrementally. ## Connect (any MCP client) ```json { "mcpServers": { "ba-agent": { "command": "uvx", "args": ["ba-agent-mcp"], "env": { "BA_AGENT_ENV_FILE": "/absolute/path/to/your/.env" } } } } ``` ## Tools | Tool | Returns | | --- | --- | | `kb_search` | Ranked KB hits with provenance (title, breadcrumb, SUPPA anchor, `data_class`). | | `kb_assemble_context` …
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.