Bruno Api MCP

🚀 Bruno API MCP Server

A Model Context Protocol (MCP) server that exposes your Bruno API collections as MCP tools. This server allows you to interact with your Bruno API collections via the MCP protocol, making your API collections accessible to AI agents and other MCP clients.

🚀 Quick Start

Why It Matters: Source Code and Data Working Together

When developers need to integrate third - party APIs, they typically face three core challenges:

1. Debugging across system boundaries: Diagnosing issues in different code and data environments is often difficult.
2. Redundant definition of API requests: Manually copying and pasting the same URLs, headers, and other configurations for each call is inefficient.
3. Version control and dependency management: As APIs change and requirements evolve, it's challenging to effectively track and manage these changes.

Bruno solves these problems. By storing API requests in files and generating a reusable tool for each request, Bruno separates code from data. This allows you to easily share API requests within your team, perform version control, and ensure everyone uses the same configurations and dependencies.

✨ Features

• Automatic conversion: Automatically convert each request in a Bruno collection into an MCP tool.
• Environment management: Support different runtime environments (e.g., development, testing, production), enabling easy switching between variables and configurations.
• Variable substitution: Substitute scalar variables in URLs, headers, and request bodies for easy request customization.
• Query parameters: Allow adding or overriding query parameters for greater flexibility.
• Custom body parameters: Specify custom parameters directly in the request body.

📦 Installation

Installation and Execution

1. Install Bruno CLI:

   npm install -g bruno
   

2. Initialize the project:

   bruno init
   

3. Add requests: Save API requests to .bruno files in the requests/ folder.
4. Generate tools:

   bruno generate
   

5. Invoke tools: Call the generated tools directly using the MCP protocol.

💻 Usage Examples

Basic Usage

Suppose there is a request file requests/get - user.bruno with the following content:

{
  "url": "{{baseUrl}}/users/{{userId}}",
  "headers": {
    "Authorization": "Bearer {{apiKey}}"
  },
  "query": {
    "include": "posts"
  }
}

When invoking, you can pass custom variables via the MCP protocol:

{
  "environment": "dev",
  "variables": {
    "userId": "123",
    "apiKey": "your - api - key"
  }
}

📚 Documentation

Pre - defined Scripts

• Start the server:

  npm start
  

• Build the project:

  npm run build
  

Contribution Guidelines

1. Clone the repository:

   git clone https://github.com/your - repo.git
   cd your - repo
   

2. Install dependencies:

   npm install
   

3. Run tests:

   npm test
   

Tool List

• Environment tool: bruno env
• Generation tool: bruno generate
• Invocation tool: bruno call

Using Custom Parameters with Tools

When calling MCP tools generated from Bruno API collections, you can provide the following custom configurations:

Environment Override

Specify a different environment to use specific variable settings:

{
  "environment": "prod"
}

Variable Substitution

Substitute variables in URLs, headers, and request bodies:

{
  "variables": {
    "userId": "123",
    "apiKey": "test - key"
  }
}

Query Parameters

Add or override query parameters:

{
  "query": {
    "page": 1,
    "per_page": 10
  }
}

Custom Body Parameters

Specify custom parameters in the request body:

{
  "body": {
    "name": "John Doe",
    "email": "john@example.com"
  }
}

Complete Example

A complete example combining all custom options:

{
  "environment": "staging",
  "variables": {
    "dealId": "abc123",
    "apiKey": "test - key - staging"
  },
  "query": {
    "limit": 5,
    "sort": "created_at"
  },
  "body": {
    "status": "active",
    "amount": 100.5
  }
}

📄 License

MIT License