# bitteprotocol/mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/BitteProtocol/mcp  
**GitHub Stars:** 14  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/bitteprotocol-mcp

## Description
Bitte Protocol integration to run AI Agents on several blockchains.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "mcp": {
    "url": "https://mcp.bitte.ai/sse"
  }
}
```

## Documentation

## What bitteprotocol/mcp MCP server does

The bitteprotocol/mcp MCP server packages Bitte AI integrations behind the Model Context Protocol. The repository description identifies its purpose as running AI agents across several blockchains, while the README lists a `bitte-ai` package for Bitte AI integrations. The available material does not enumerate individual MCP tools, supported blockchain networks, transaction operations, or chain-specific configuration.

A hosted service is available at `https://mcp.bitte.ai/sse`. This gives MCP clients an SSE endpoint to connect to without requiring the repository to be built locally. The project also contains the source and development workflow for the Bitte AI service.

## How it works

MCP clients connect to the hosted SSE URL as a remote server. The README includes a Cursor configuration that registers the server under the `bitte-ai` name:

```json
{
  "mcpServers": {
    "bitte-ai": {
      "url": "https://mcp.bitte.ai/sse"
    }
  }
}
```

The bitteprotocol/mcp MCP server is organized as a monorepo, with packages for individual services. At the time described by the README, the listed package is `bitte-ai`. Bun provides the JavaScript runtime, and Turborepo manages the monorepo workflow. Biome is used for code-quality tasks.

## Setup and configuration

For client use, add the hosted SSE URL to an MCP-compatible client configuration. The supplied example specifically documents Cursor. No API key, wallet setting, blockchain network variable, or other environment variable is documented in the provided material.

For repository development, install dependencies with `bun install`. The available scripts include `bun run build` to build all packages, `bun run start` to start both services, and `bun run dev` for development mode. The Bitte AI service can be run individually with `bun run dev:bitte-ai`. Formatting and lint checks use `bun run check`, with `bun run check:fix` available for automatic fixes.

These commands describe working on the monorepo rather than installing a standalone package for end users. The README does not provide a package-manager command that launches the hosted MCP service as a directly runnable local server.

## Tools and capabilities

The supported capability described here is Bitte AI integration for AI agents operating across several blockchains. The repository exposes that integration through MCP and provides a remote SSE connection point. Because no tool list appears in the supplied README, tool names and exact actions should be confirmed from the live service or source before building an agent workflow around them.

The documented client configuration supports connecting Cursor to the hosted endpoint. Other clients may support the same MCP transport, but the provided material does not name or configure them.

## Limitations and notes

The README does not specify authentication requirements, supported chains, available tools, request schemas, rate limits, or production availability guarantees. It also does not include a license declaration. Treat the hosted endpoint and the repository development commands as separate options: the endpoint is for client connection, while the Bun commands are for developing the monorepo.

_Full upstream README: https://allmcps.com/mcp/bitteprotocol-mcp/readme_