About IB API Documentation
IB API Documentation is an MCP server for retrieving documentation from Postman collections and generating code actions. It is intended for developers who need to inspect API requests and examples or produce TypeScript/JavaScript actions from them.
Key features
- 01List and search Postman collections
- 02Browse collection structures
- 03Retrieve request details
- 04Inspect response examples
- 05Generate code actions from requests
Use cases
- 01Find a request in Postman collections
- 02Review request and response example details
- 03Generate TypeScript/JavaScript actions from API requests
MCP support
Provides MCP tools for accessing Postman collection documentation and generating actions from requests.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEIB API Documentation
A Model Context Protocol (MCP) server that provides tools for retrieving documentation from Postman collections and generating AI actions.
Features
- List and search Postman collections
- Navigate collection structures
- Get detailed request information | - Comprehensive response example handling: | - List available response examples | - Get request details (focused on request information) | - Get detailed response example information | - Efficient workflow for accessing example data
- Generate code actions from Postman requests
- Optional integration with multiple AI frameworks
- TypeScript/JavaScript code generation
Documentation
- API Reference - Detailed information about server tools and data structures
- Configuration Guide - Server setup and configuration options
- Prompt Templates - Examples and templates for using the tools
- Update Instructions - How to update your MCP server installation
Installation
- Clone the repository:
git clone https://github.com/ibproduct/ib-api-doc.git
cd ib-api-doc
- Install dependencies:
npm install
- Build the server:
npm run build
- Configure the server following the Configuration Guide
Usage
See the Prompt Templates guide for detailed usage instructions and examples.
Development
Development Workflow
- Set up development environment:
# Clone and set up the repository
git clone https://github.com/ibproduct/ib-api-doc.git
cd ib-api-doc
npm install
- Configure development server:
- Create a development configuration in your MCP settings file
- Point it to your local development build
- Include all tools in the alwaysAllow array
- Development cycle:
# Make code changes
npm run build # Build the changes
# Reload VSCode window to pick up new build
# Test using the development server configuration
# Repeat until satisfied with changes
- Before committing:
- Test all affected functionality
- Update documentation if needed
- Follow the git workflow below
Git Workflow
- Before starting development:
git pull origin main
npm install # If dependencies have changed
- During development:
- The
.gitignorefile is configured to exclude:- Build artifacts (
build/,dist/) - Dependencies (
node_modules/) - Environment files (
.env*) - IDE files (
.vscode/,.idea/) - Logs and debug files
- System files (
.DS_Store,Thumbs.db)
- Build artifacts (
- Committing changes:
git add . # Stage changes (respects .gitignore)
git commit -m "type: description
- Bullet points for specific changes
- Another change"
- Pushing changes:
git pull origin main # Get latest changes
git push origin main # Push your changes
Development Server
To run the server in development mode with automatic reloading:
npm run watch
To inspect the server's capabilities:
npm run inspector
License
Private - IntelligenceBank © 2024
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.