monograph-mcp
Related Servers
Alternatives to monograph-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to work with estimates, quotes, job schedules, variations, and progress claims in a user's signed-in Buildxact account, with write actions requiring approval by default.Elastic 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to work with estimates, schedules, daily logs, bills, and invoices in a signed-in BuildBook account, with write operations reviewed before approval.7Elastic 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to operate a user's signed-in Joist account, creating estimates, sending invoices, managing clients, and reviewing overdue payments through natural language without a Joist API key. It supports hosted MCP access plus a local stdio server for clients that require it.7Elastic 2.0

TabBridgeofficial
AlicenseNot gradedqualityBmaintenanceLets any MCP-speaking AI agent drive your everyday Chrome browser, opening pages, reading them, clicking, typing, taking screenshots, and inspecting DevTools console, network, storage and performance data with your existing sign-ins. Risky actions like submitting or paying require your explicit approval, and agents are confined to their own tab group with secrets hidden.Apache 2.0- AlicenseAqualityBmaintenanceEnables AI agents to work inside a user's signed-in Buildertrend account, reading job schedules, identifying late tasks, writing daily logs, and producing progress updates without requiring a Buildertrend API key.7Elastic 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive Chrome through MCP tools for navigating pages, taking token-efficient snapshots and diffs, finding and acting on elements, and capturing screenshots. Sensitive actions such as submitting forms, downloading or uploading files, and running JavaScript require human approval through a system dialog.MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: guide, readiness check, opening a session, reading the page, clicking, typing, and closing. The boundaries between setup, interaction, and teardown are obvious, with almost no risk of tool misselection.
All tools share the same monograph_ prefix and use short lower_snake_case names. The pattern is predictable throughout, with only guide/status being nouns and the rest actions, which is still highly consistent.
Seven tools are well-scoped for a browser automation wrapper: just enough to cover setup, page interaction, and cleanup. No tool feels redundant or out of place.
The set covers the core browser lifecycle: guide, status, open, read, click, type, and close. Minor gaps exist for general browser operations like scrolling, selecting dropdown options, or explicit navigation, but agents can likely work around them.