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.Full API Lifecycle Support
Covers all processes from API discovery to deployment and monitoring
Dual Protocol Support
Can work over both HTTP and WebSocket connections
Optimized for Developers
Tools optimized for API integration, testing, and debugging
Secure Authentication
Bearer token-based secure access control
Real-Time Analytics
API usage, performance, and traffic analysis
Automatic Token Management
Automatic token acquisition for JWT and OAuth2 protocols
Target Users
API Developers
For API integration and testing operations
DevOps Teams
For API monitoring and performance analysis
Project Managers
For API usage statistics and reports
QA Teams
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_apis
Search and filter APIs on the Portal. Can search by name, category, tags, etc.
get_api_details
Get detailed information of a specific API. API metadata, endpoints, and documentation
get_api_spec
Get API’s OpenAPI (Swagger) specification. All endpoints, schemas, and examples
get_api_access_url
Get API’s full access URL. Base URL for testing operations
get_api_auth_info
Get API’s authentication information. JWT/OAuth2 server addresses and client information
get_api_plans
List API’s available plans. FREE, SUBSCRIPTION, METERED, and TIERED plan details
get_api_applications
List applications registered to a specific API
Application Management
search_apps
List and search applications owned by the user
create_app
Create new application. Used to group API subscriptions
get_app_details
Get detailed information of a specific application
get_app_apis
List APIs registered to the application
get_app_registrations
List all API registrations of the application
delete_app
Delete application (all registrations and credentials are also deleted)
get_available_apis_for_app
List available APIs for the application
API Registration and Subscription
register_api_to_application
Register application to an API and select a plan
Credentials Management
get_app_credentials
List all API keys of the application (including username/password values)
add_api_key
Add new API key to the application
get_credential_details
Get detailed information of a specific credential (including real values)
delete_credential
Delete and revoke API key
Token and Authentication
get_token
Get JWT/OAuth2 access token. Supports automatic or manual mode
API Testing
test_api
Test API endpoints. Send HTTP requests and receive responses
Analytics and Statistics
get_api_traffic
Get API traffic analytics data. Volume, patterns, and usage trends
get_api_response_time
API response time analytics. Latency trends and performance statistics
get_api_stats
General API statistics. Request count, error rates, usage patterns
query_api_traffic
Detailed traffic queries. Complex filtering, sorting, and aggregation features
Helper Tools
hello
Get greeting message from Apinizer API Portal (connection test)
Important Notes
Authentication: All tools require
APINIZER-TOKEN headerTwo 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 endpointAuthorization: Application owners can only access their own applications

