add: Causeway - #8
Open
EmergenceDeveloper wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
Causeway is a standalone Rust MCP server that gives an AI a real Chromium browser through Chrome DevTools Protocol. The current source registers 52 tools for navigation, tabs, clicks, typing, forms, reading, JavaScript, screenshots, downloads, PDFs, device emulation, WebMCP discovery, and batched browser actions.
The listing points to the official product page and repository, and uses the source-grounded custom license and free local-binary model.
Source grounding
Maintainer notes
The new file follows the repository's current
content/tools/*.mdfrontmatter shape. I left outopen_sourcebecause the custom license is not identified as an OSI or SPDX license, and I left out platforms and logo metadata because the upstream source does not settle those fields. The website guide appears to describe an older content shape; please adjust any field names you want normalized before merging.