Schema | @loggydev/mcp-server

@loggydev/mcp-server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`LOGGY_API_URL`	No	API URL (default: https://loggy.dev)	https://loggy.dev
`LOGGY_API_TOKEN`	Yes	Your Loggy API token (get one from Settings → API Tokens)

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
list_heartbeatsB	List all heartbeat monitors for your account
create_heartbeatA	Create a new heartbeat monitor for cron jobs or scheduled tasks
get_heartbeatB	Get details of a specific heartbeat by ID or slug
delete_heartbeatC	Delete a heartbeat monitor
list_uptime_monitorsA	List all uptime monitors
create_uptime_monitorB	Create a new uptime monitor to check URL availability
delete_uptime_monitorB	Delete an uptime monitor
list_status_pagesA	List all status pages
create_status_pageB	Create a new public status page
list_feature_flagsB	List all feature flags
create_feature_flagC	Create a new feature flag
toggle_feature_flagB	Enable or disable a feature flag
list_alertsC	List recent alerts
list_projectsB	List all projects
get_project_logsB	Get recent logs for a project

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/loggy-dev/loggy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server