API Portal Usage with Model Context Protocol (MCP)
Overview
The API Portal project contains tools that provide various API management functions using the Model Context Protocol (MCP) standard. These tools are MCP-accessible versions of the API Portal Management API.
Covers all processes from API discovery to deployment and monitoring
Can work over both HTTP and WebSocket connections
Tools optimized for API integration, testing, and debugging
Bearer token-based secure access control
API usage, performance, and traffic analysis
Automatic token acquisition for JWT and OAuth2 protocols
Target Users
For API integration and testing operations
For API monitoring and performance analysis
For API usage statistics and reports
For API test scenarios and validation operations
Technical Requirements
- Valid Apinizer Portal account
- APINIZER-TOKEN authentication header
- MCP compatible client (Claude, VS Code extensions, etc.)
- Internet connection (for API Portal access)
MCP (Model Context Protocol) provides client-server communication using the JSON-RPC 2.0 protocol. Unlike HTTP REST API, this protocol offers bidirectional messaging over persistent connections, cannot be tested directly with tools like curl/Postman, and requires special MCP clients like Claude Desktop.
API Management and Discovery
Search and filter APIs on the Portal. Can search by name, category, tags, etc.
Get detailed information of a specific API. API metadata, endpoints, category names, and documentation
Get API's OpenAPI (Swagger) specification. All endpoints, schemas, and examples
Get API's full access URL. Base URL for testing operations
Get API's authentication information. JWT/OAuth2 server addresses and client information
List API's available plans. FREE, SUBSCRIPTION, METERED, and TIERED plan details
List applications registered to a specific API
List all API categories in the portal. Returns category IDs and names
Application Management
List and search applications owned by the user
Create new application with automatic API key generation. Used to group API subscriptions
Get detailed information of a specific application
List APIs registered to the application
List all API registrations of the application
Delete application (all registrations and credentials are also deleted)
List available APIs for the application
API Registration and Subscription
Register application to an API and select a plan
Credentials Management
List all API keys of the application (including username/password values)
Add new API key to the application
Get detailed information of a specific credential (including real values)
Delete and revoke API key
Token and Authentication
Get JWT/OAuth2 access token. Supports automatic or manual mode
API Testing
Test API endpoints. Send HTTP requests and receive responses
Analytics and Statistics
Get API traffic analytics data. Volume, patterns, and usage trends
API response time analytics. Latency trends and performance statistics
General API statistics. Request count, error rates, usage patterns
Detailed traffic queries. Complex filtering, sorting, and aggregation features
Helper Tools
Get greeting message from Apinizer API Portal (connection test)
Important Notes
Authentication: All tools require APINIZER-TOKEN header
Two Protocols: Both HTTP and WebSocket protocols are supported
Testing Operations: To test API, first get base URL with get_api_access_url, then add the endpoint
Credentials: get_app_credentials and get_credential_details return real API Key/Secret values. Store this information securely.
Authorization: Application owners can only access their own applications