Schema | BIP Monitor MCP Server

BIP Monitor MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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`	{}
`resources`	{}

Functions exposed to the LLM to take actions

Name	Description
start_dev_serverC	Start the Next.js dev server and monitor it for errors
get_errorsB	Get recent errors from the dev server with filtering options
clear_errorsB	Clear the error log and start fresh
stop_dev_serverC	Stop the running dev server
get_statusA	Get current status of the dev server
attach_to_dev_serverC	Attach monitoring to an existing dev server process (allows status bar visibility when started with Bash tool)
detach_dev_serverA	Stop watching an attached dev server (does not stop the actual process)
get_logsB	Get application logs with flexible line limits and optional filtering

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`Recent Errors`	Last 100 errors from the dev server with categorization and suggestions
`App Status`	Current status of the dev server (running/stopped/crashed)
`Recent Application Logs`	Last 100 lines from application log (use get_logs tool for more control)
`Performance Metrics`	Compile times, build times, and performance stats

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/The-Bip-App/bip-monitor-mcp'

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