MCPs › Dev tools › clariBI.com

clariBI.com● live

clariBI exposes a Model Context Protocol server so external LLM clients (Claude Desktop, Cursor, ChatGPT custom GPTs, generic MCP-aware agents) can create accounts, upload CSV / Excel / JSON / PDF files (inline or by URL, with server-side SSRF guard), connect Google Ads / Analytics 4 / Search Console / Sheets / Drive / BigQuery / Meta Ads / Jira / Confluence via OAuth handoff, run natural-language analyses against connected sources, and generate reports. 19 tools, 3 resources, 2 prompts. OAuth 2.1 with Dynamic Client Registration and PKCE plus API-key fallback. Streamable HTTP and SSE transports. Python and TypeScript SDKs, codegen-driven from the live tool catalog.

listed on

Smithery

Install clariBI.com

For anyone using clariBI.com — no Lulu account needed

npx -y @smithery/cli@latest install darek/claribi --client claude

The MCP Growth Kit — grow the server you just found

9 field-tested tactics as a designed playbook plus skills your coding agent can run. Free.

Get the Kit →

FAQ

How do I install clariBI.com in Claude Code?

clariBI.com installs from source — follow the repository README.

Which registries list clariBI.com?

smithery

What is clariBI.com's trust score?

24 out of 100, computed from cross-registry traction signals (installs, stars, registry presence) — never influenced by sponsorship.

Similar servers

MMeteomatics26The Meteomatics MCP (Model Context Protocol) server allows AI agents to securely access Meteomatics weather data tools. MCP is an open standard that lets AI applications connect to external tools and data sources. With the Meteomatics MCP, agents can request weather data directly from the Meteomatics API through a secure /mcp endpoint. The MCP server manages authentication using OAuth (client registration, authorization code + PKCE, and refresh tokens). Once connected, the AI agent can access data, models, parameters, time ranges that are available to your Meteomatics API account. same category · 30% description match Eemblem-mcp29# EmblemAI MCP EmblemAI is a hosted Model Context Protocol server that gives AI agents a full-featured crypto wallet plus **200+ tools** for trading, DeFi, NFTs, and on-chain analytics across **7 blockchains**: - **Bitcoin** — native BTC, Ordinals inscriptions, Runes, BRC-20, Stamps / SRC-20, Alkanes, rare sats - **Solana** — SOL + SPL tokens, Jupiter-routed swaps, Solana memecoin discovery, RugCheck - **Ethereum** — native ETH, ERC-20, ERC-721 / ERC-1155 NFTs, ETH swaps - **Base** — native ETH on L2, ERC-20, NFTs, Clanker discovery - **BSC** — native BNB, BEP-20, FourMeme bonding-curve discovery and trading - **Polygon** — native MATIC, ERC-20, swaps - **Hedera** — HBAR, HTS tokens, MemeJob discovery and trading Plus prediction markets via **Polymarket**, market research, conditional orders (limit / stop-loss / take-profit) on supported chains, and on-chain analytics. ## Quick start The Smithery deployment connects directly to the hosted EmblemAI MCP at `https://emblemvault.ai/api/mcp`. You only need an API key: 1. Sign in at [emblemvault.ai](https://emblemvault.ai). 2. Open **Settings → Vault Access Key** and copy your key. 3. Paste it as the `apiKey` parameter in the Smithery connection form. Browsing tools (`tools/list`) works anonymously, so you can inspect the catalog before authenticating. ## Auth modes | Mode | When to use | Scope | | --- | --- | --- | | **API key** (`x-api-key`) | Unattended agents, cron jobs, server-to-server, any workflow that mints tokens or sends transactions | Full read + write, no expiry until revoked | | **OAuth 2.0 + PKCE** (RFC 7591 Dynamic Client Registration) | Interactive sessions where a human can click a browser popup | Read-only `vault:read`, short-lived JWT | | **x402 micropayments** | Pay-per-call across the public catalog without an account | Per-tool-call USDC settlement | The Smithery deployment defaults to the API-key path, configured via the `apiKey` parameter (sent to the upstream as the `x-api-key` header). ## Enabling transactional tools State-changing tools (sends, swaps, mints, conditional-trade creates) are hidden by default. Opt in by setting the `enableTransactions` parameter to `enabled` — Smithery's gateway forwards it as the `x-mcp-transactions: enabled` header. Transactional tools then surface in `tools/list` with a `-transaction` suffix, which makes them easy to allow- or block-list with wildcard rules in the host client. Note: transactional tools also require API-key auth — OAuth bearers do not pass the `vault:write` gate. ## Specialized listings (filter) The full 200-tool surface is wide. For Bitcoin-only, Solana-only, or any other curated slice, use the stdio bridge `@emblemvault/mcp` (npm) and set: ``` EMBLEMAI_TOOLS_FILTER="bitcoin*,*Rune*,*Inscription*" ``` The bridge applies the glob filter to both `tools/list` and `tools/call`, exposing only the matching subset to the host LLM. The hosted Smithery deployment always exposes the full catalog; the filter is a stdio-side feature. ## Categories Trading · DeFi · NFTs · Wallet · Bitcoin Ordinals · Polymarket prediction markets · Cross-chain · Market analytics · Research / web search. ## Links - Hosted MCP: `https://emblemvault.ai/api/mcp` - Stdio bridge: `@emblemvault/mcp` ([github](https://github.com/EmblemCompany/Agent-skills/tree/main/mcp-bridge)) - Repo: [EmblemCompany/Agent-skills](https://github.com/EmblemCompany/Agent-skills) - Web app: [emblemvault.ai](https://emblemvault.ai) - Glama listing: [glama.ai/mcp/servers/EmblemCompany/Agent-skills](https://glama.ai/mcp/servers/EmblemCompany/Agent-skills) - Docs: [emblemvault.ai/docs/mcp](https://emblemvault.ai/docs/mcp) ## License MIT (stdio bridge + documentation). Hosted MCP is managed SaaS.