mcp-venmo
Related Servers
Alternatives to mcp-venmo
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceMCP server that wraps sendblue-browser-use's HTTP API, providing tools to control a stealth-patched Chromium browser with persistent sessions, navigation, screenshots, and script execution.3MIT- AlicenseBqualityDmaintenanceBrowser automation MCP server using Camoufox anti-detect browser with fingerprint spoofing, geolocation/timezone spoofing, and human-like cursor movement.141Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI agents and human operators drive isolated Chromium profiles with their own cookies, fingerprints, and proxies, exposing tools for navigation, clicking, typing, extraction, screenshots, JavaScript evaluation, tabs, cookies, and waits. Because session and login state persist per profile, agents can carry out real authenticated workflows across sessions.MIT
- AlicenseNot gradedqualityAmaintenanceThis server enables MCP clients and AI agents to perform browser automation with Playwright-compatible tools, persistent profiles, extensions, proxy support, and humanized interactions. It can be run via npm or Docker over stdio or Streamable HTTP for web research, automation, testing, and regional QA.431 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for controlling a local camofox-browser instance, enabling LLM agents to perform web automation tasks such as navigation, interaction, snapshotting, and content extraction.92 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.1 npmISC
TDQS
Scored across 13 tools
Each tool targets a distinct Venmo operation—payments, requests, transactions, friends, cards, transfers, and login—so an agent can easily select the right one. Minor overlap between get_transactions and get_notifications is resolved by their focused descriptions.
All tools follow a consistent 'venmo_verb_noun' pattern (e.g., venmo_get_balance, venmo_send_payment, venmo_accept_request) with clear, action-first verbs and no style mixing.
At 13 tools, the server is well-scoped for a Venmo integration, covering authentication, balance, payments, requests, transactions, friends, cards, and bank transfers without excessive granularity.
Core Venmo workflows are fully covered: send/request money, view balance and transactions, manage friends, and transfer to bank. Slight gaps include no explicit accept/decline for friend requests and no logout, but these are edge cases, not critical dead ends.