Pingera MCP Server
Officialby pingera
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_HOST | No | Host to bind to in SSE mode | 0.0.0.0 |
| HTTP_PORT | No | Port to listen on in SSE mode | 5000 |
| PINGERA_MODE | No | Operation mode: read_only (default) or read_write | read_only |
| PINGERA_DEBUG | No | Enable debug logging | false |
| TRANSPORT_MODE | No | Transport mode: stdio (default) or sse | stdio |
| PINGERA_API_KEY | No | Your Pingera API key (required if not using JWT token) | |
| PINGERA_TIMEOUT | No | Request timeout in seconds | 30 |
| PINGERA_BASE_URL | No | API endpoint URL | https://api.pingera.ru/v1 |
| PINGERA_JWT_TOKEN | No | Your Pingera JWT token (alternative to API key) | |
| PINGERA_MAX_RETRIES | No | Maximum retry attempts | 3 |
| PINGERA_SERVER_NAME | No | Server display name | Pingera MCP Server |
| REQUIRE_AUTH_HEADER | No | Require Authorization header in SSE mode | false |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pingera/pingera-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server