PostPulse
Officialby PostPulse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server bind address | 0.0.0.0 |
| PORT | No | Server port | 3000 |
| REDIS_URL | Yes | Redis connection URL for session/event persistence (required) | |
| PUBLIC_URL | No | Public-facing URL (for OAuth metadata discovery) | |
| POSTPULSE_API_URL | No | PostPulse API base URL | https://api.post-pulse.com |
| POSTPULSE_AUDIENCE | No | API audience | https://api.post-pulse.com |
| POSTPULSE_AUTH_ISSUER | No | Auth0 issuer URL | https://auth.post-pulse.com/ |
| POSTPULSE_AUTH_JWKS_URI | No | JWKS endpoint | https://auth.post-pulse.com/.well-known/jwks.json |
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/PostPulse/mcp-server-postpulse'
If you have feedback or need assistance with the MCP directory API, please join our Discord server