LiDAR Harness MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| harness_initA | Initialize LiDAR Harness for a project: detect typecheck/lint commands, establish baselines, classify task complexity. Call this ONCE at the start of a session. Provide the user's task message for complexity classification. Returns: session info with detected commands, complexity, and PGO readiness. |
| harness_classifyA | Classify a task as "simple" (question, explanation) or "complex" (implementation, refactor, fix). Simple tasks skip PGO and review overhead entirely. Call before starting work. |
| harness_pgoA | Run incremental PGO (Pose Graph Optimization) typecheck/lint verification. KEY CONCEPT: Only returns NEW errors not seen in previous calls. If you call it 10 times, each call only shows errors that appeared SINCE the last call. When it returns 0 new errors, the code compiles cleanly. Use after each agent turn that modifies code to verify incrementally. |
| harness_reviewA | Run multi-perspective code review: security scan (secrets in git diff), correctness (uncommitted changes), style (lint results). Call periodically (e.g. every 3rd turn) to catch issues the agent might miss. |
| harness_resetA | Reset PGO baselines and shown-errors state for a fresh start. Call when switching to a new task or after significant dependency changes. |
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/bernardleex526-png/lidar_harness_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server