mpulse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MPULSE_API_TOKEN | Yes | Your pre-issued mPulse API token (mPulse -> your name -> Account -> Generate/Revoke API Token). | |
| MPULSE_APPS_CONFIG | No | Path to the mPulse apps registry JSON file. Defaults to ./mpulse_apps.json. | ./mpulse_apps.json |
| MPULSE_API_TOKEN_APP_B | No | Override API token for app-b if configured with a different api_token_env. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_summaryA | Aggregate summary stats for one timer (median, margin-of-error, count, p95, p98). mPulse query-type: Time selection (exactly one required):
Timer: Drilldowns filter the data (e.g. Set |
| get_histogramA | Distribution (histogram buckets) for one timer over the period. mPulse query-type: Use |
| get_timersA | A single timer's value by minute over time (time series). mPulse query-type: Returns a series of {x, y} points at per-minute resolution for the selected
calendar day (or |
| get_metricsA | Multiple timers/metrics by minute over time. mPulse query-type: Time selection and drilldowns behave as in the other tools (single calendar
day OR relative |
| queryA | Call an arbitrary mPulse query-type with arbitrary parameters. Use this for query-types not covered by the explicit tools (see
|
| list_appsA | List registered mPulse apps and the default app. Use this before other tools so you reference real app names. The |
| list_query_typesA | List the mPulse query-types this server knows about, with one-line summaries. The explicit tools cover: summary→ |
| describe_queryA | Describe a query-type: parameters, drilldowns, response shape, and caveats. Pass a slug from |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/hyoon2007/mpulse-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server