Butterbase is an open-source backend-as-a-service that gives applications managed building blocks such as Postgres data, authentication, file storage, serverless functions, an AI gateway, and an MCP server. It is for developers building AI-driven applications and backend services. The catalogue add-ons operate or integrate with Butterbase through its agent-oriented interfaces.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/butterbase-ai/butterbaseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/butterbase-ai/butterbase/react-vite-butterbase)<a href="https://agentmods.dev/mcp/butterbase-ai/butterbase/react-vite-butterbase"><img src="https://agentmods.dev/badge/mcp/butterbase-ai/butterbase/react-vite-butterbase.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
butterbase scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"butterbase": {
"url": "{{API_URL}}/mcp",
"headers": {
"Authorization": "Bearer ${BUTTERBASE_API_KEY}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 8 lines scan A 9f8b2b31481c
butterbase is an MCP server published in the GitHub repository butterbase-ai/butterbase (3,464 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
supabase
Lets the agent manage Supabase projects: inspect tables, run SQL, handle migrations and read logs. Runs locally from the @supabase/mcp-server-supabase npm package. Needs 1 environment variable to run.
postgres
Lets the agent inspect a PostgreSQL database schema and run read-only SQL queries against it. Runs locally from the @modelcontextprotocol/server-postgres npm package.
perplexity
MCP server "perplexity" as configured in tdimino/claude-code-minoan. Runs /path/to/perplexity-mcp/build/index.js with node. Needs 1 environment variable to run.
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.
dbeast
MCP server "dbeast" as configured in snss10/DBeast. Runs ${workspaceFolder}/dbeast/src/server.py with python. Needs 9 environment variables to run.
AWSPostgres
MCP server "AWSPostgres" as configured in spacehendrix/clauder. Runs locally from the awslabs.postgres-mcp-server@latest Python package. Needs 3 environment variables to run.