Developer · Remote MCP server
butterbase-ai MCP
Butterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.butterbase-ai/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-01
- Updated
- 2026-06-01
- Publisher
- butterbase-ai (GitHub)
- Website
- butterbase.ai
- Repository
- github.com/butterbase-ai/butterbase-oss (folder services/mcp-server)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.butterbase.ai/mcp | Authorization (required, secret) |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @butterbase/mcp | 1.0.0 | stdio |
How to connect butterbase-ai MCP
butterbase-ai MCP is a remote MCP server: there is nothing to install. Its endpoint is https://api.butterbase.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @butterbase/mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @butterbase/mcp@1.0.0. It reads the environment variable BUTTERBASE_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@butterbase/mcp@1.0.0"
],
"env": {
"BUTTERBASE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Bus MCPMCP server fronting a self-hosted coordination-bus HTTP API: post/read/claim/release/heartbeat. | Local · stdio |
| Busca de CEPReturns the postal code (CEP) and standardized address from the Brazilian Post from a given address. | Remote · HTTP |
| Bussin MCPMCP server for Azure Service Bus. Peek, search and replay dead-letter messages from any MCP client. | Local · stdio |
| Busymate DevToolsCapture, inspect & debug HTTPS traffic across iOS, Android, browsers & backends — 304 MCP tools. | Remote · HTTP |
| BuyAPIVendor intelligence for AI coding agents choosing developer tools and stacks. | Remote & Local · HTTP, stdio |
| Byterovermemory MCPA paid remote MCP for OpenAI Codex memory MCP, built to return verdicts, receipts, usage logs, and a. | Remote · HTTP |
| C# Class Analyzer MCPA read-only MCP server that lets an AI assistant browse any C# solution through Roslyn. | Local · stdio |
| C2padisclosure MCPRemote MCP for C2PA disclosure policy MCP, structured receipts, audit logs, and reviewer-ready evide. | Remote · HTTP |